Product release system, method and device having a customizable prepurchase function

ABSTRACT

A product release system, method and device that enables product controllers to generate product listings for one or more products as well as one or more customized prepurchase events for each of the products. The product release system, method and device then executes the prepurchase events according to one or more pricing, timing and permission conditions specified for each of the prepurchase events, facilitates the purchasing of the products during the prepurchase events and notifies the product controllers of the results of the prepurchase events.

FIELD OF THE INVENTION

The present invention relates to the field of new product releases.Specifically, the present invention relates to a product release system,method and device that enables customizable prepurchases before a newproduct's regularly scheduled public release date.

BACKGROUND OF THE INVENTION

The advent of ecommerce has created exciting product launchopportunities for the creators of new physical and digital products.Product creators use third-party controlled ecommerce merchants andmarketplaces (herein referred to as “online merchants”) to reachconsumers around the globe.

Because online merchant “shelf space” is virtual rather than physical,this shelf space is infinitely scalable at low cost. This low costscalability allows online merchants to list and sell a wider variety ofproducts from more product creators than ever before. The low cost ofvirtual shelf space also allows online merchants to continue listing andselling even low-selling products long after most physical brick andmortar stores would have discontinued them.

Product listings can forever occupy the online merchant's virtualshelves, forever competing against one another for the attention ofconsumers. As a result, it's more difficult than ever for productcreators to make their product listings stand out. The competition forproduct discoverability is fierce. Every day from this day forward, anyindividual or company that wants to sell anything online will facevirtual shelves glutted with competition that grows more glutted by theday.

Product creators begin planning their new product introductions monthsor years in advance. The product creator will often evaluate theirproduct development schedule, consider logistical and seasonal productmarketing considerations, and then create a product launch timeline torelease the product at a future date. Their product development,manufacturing and marketing will revolve around this single productrelease date.

For consumers, new product introductions are exciting because newproducts promise important innovations over what came before. Often,what's coming and what's new is more exciting to consumers than olderproducts.

This consumer preference for new and upcoming products creates uniquechallenges for product creators and their marketing teams, especiallywhen considering the finality of the product introduction date. It meansthe product creator has only one chance to make a splash before theirupcoming new product launch event becomes yesterday's news.

SUMMARY OF THE INVENTION

A product release system, method and device that enables productcontrollers to generate product listings for one or more products aswell as one or more customized prepurchase events for each of theproducts. The product release system, method and device then executesthe prepurchase events according to one or more pricing, timing andpermission conditions specified for each of the prepurchase events,facilitates the purchasing of and/or access to the products during theprepurchase events and notifies product creators of the results of theprepurchase events.

A first aspect is directed to a product release system for enablingprepurchase of one or more products. The product release systemcomprises one or more servers including a processor and a non-transitorycomputer-readable medium coupled with the processor, storing a productrelease platform having a user interface and able to be communicativelycoupled with one or more third party devices over a network, wherein theproduct release platform is operable to generate a product listingidentifying a product based on product data received from a third partydevice, wherein the product data includes a product release date, andmetadata associated with the product, generate one or more prepurchasekeys and one or more prepurchase events based on prepurchase data forthe product indicated by the third party device, wherein the prepurchasedata includes a starting time, an end condition and pricing data foreach of the prepurchase events, wherein the starting time is before theproduct release date and for each of the prepurchase events, facilitateaccess to the product to one or more customers during the prepurchaseevent if one or more keys submitted by the customers correspond to theprepurchase keys associated with the prepurchase event and preventaccess to the product to the one or more customers during theprepurchase event if the one or more keys submitted by the customers donot correspond to the prepurchase keys associated with the prepurchaseevent.

In some embodiments, each of the keys is included within a hyperlinkthat links to a page associated with the prepurchase event of that keyand submits the key to the product release platform for determining ifthe key corresponds to the prepurchase keys associated with theprepurchase event. In some embodiments, the end condition is one or moreof an end time, a quantity of sales, a maximum quantity of customersaccessing the prepurchase event, an inventory status of the product, anda manual cancellation of the event, and further wherein, for each of theprepurchase events, upon reaching the end condition the product releaseplatform is operable to terminate the prepurchase event. In someembodiments, the pricing data is a pricing metric that indicates a pricevalue for the starting time and one or more subsequent times between thestarting time and an end of the prepurchase event as indicated by theend condition. In some embodiments, the prepurchase data includes one ormore prepurchase conditions, and further wherein, for each of theprepurchase events, the product release platform is operable to preventsales of the product to one or more of the consumers even if thesubmitted key corresponds to the prepurchase keys associated with theprepurchase event if the one or more of the consumers have not satisfiedthe prepurchase conditions.

In some embodiments, the prepurchase conditions comprise one or more ofsubmitting contact information, purchasing or subscribing to one or moreother products spending a threshold amount of money and agreeing to aterms of use of the product. In some embodiments, an account database isstored on the non-transitory computer-readable medium and includes aplurality of accounts each having a set of customer contact information,and further wherein, for each of the prepurchase events, the prepurchasedata includes identification of all or a subset of one of the sets ofcustomer contact information and the product release platform isoperable to transmit the prepurchase key to network accessible locationsidentified by the subset of the one of the sets of customer contactinformation. In some embodiments, the product release platform isoperable to add the contact information submitted to satisfy theprepurchase conditions to the one of the sets of customer contactinformation of the account associated with the prepurchase event.

In some embodiments, for each of the prepurchase events, the productrelease platform is operable to generate a prepurchase listing thatidentifies the product based on the metadata, the release date of theproduct and the starting time of the prepurchase event. In someembodiments, the product release platform is operable to generate one ormore prepurchase preorder keys and one or more prepurchase preorderevents based on prepurchase preorder data for the product indicated bythe third party device, wherein the prepurchase preorder data includesinformation that identifies one of the prepurchase events, for each ofthe prepurchase preorder events, facilitate ordering of the product byone or more customers during the prepurchase preorder event if one ormore prepurchase preorder keys submitted by the customers correspond tothe prepurchase preorder keys associated with the prepurchase preorderevent and prevent ordering of the product by the one or more customersduring the prepurchase preorder event if the one or more prepurchasepreorder keys submitted by the customers do not correspond to theprepurchase preorder keys associated with the prepurchase preorder eventand facilitate the purchase of the product by the one or more customersthat ordered the product during the identified one of the prepurchaseevents. In some embodiments, the product data includes a content filecontaining the product and the content file comprises one or more of thegroup consisting of: a digital book, an image, a video, audio, acomputer application.

A second aspect is directed to a method of enabling prepurchase of oneor more products via one or more product release servers. The methodcomprises generating, with the product release servers, a productlisting identifying a product based on product data received from athird party device, wherein the product data includes a product releasedate, and metadata associated with the product, generating, with theproduct release servers, one or more prepurchase keys and one or moreprepurchase events based on prepurchase data for the product indicatedby the third party device, wherein the prepurchase data includes astarting time, an end condition and pricing data for each of theprepurchase events, and wherein the starting time is before the productrelease date and for each of the prepurchase events, with the productrelease servers, facilitating access to the product to one or morecustomers during the prepurchase event if one or more keys submitted bythe customers correspond to the prepurchase keys associated with theprepurchase event and preventing sales of the product to the one or morecustomers during the prepurchase event if the one or more keys submittedby the customers do not correspond to the prepurchase keys associatedwith the prepurchase event.

In some embodiments, each of the keys is included within a hyperlinkthat links to a page associated with the prepurchase event of that keyand submits the key to the product release servers for determining ifthe key corresponds to the prepurchase keys associated with theprepurchase event. In some embodiments, the end condition is one or moreof an end time, a quantity of sales, a maximum quantity of customersaccessing the prepurchase event, an inventory status of the product andmanual cancellation of the event, and further wherein, for each of theprepurchase events, upon reaching the end condition the product releaseplatform is operable to terminate the prepurchase event. In someembodiments, the pricing data is a pricing metric that indicates a pricevalue for the starting time and one or more subsequent times between thestarting time and an end of the prepurchase event as indicated by theend condition. In some embodiments, the prepurchase data includes one ormore prepurchase conditions, further comprising, for each of theprepurchase events, preventing sales of the product to one or more ofthe consumers with the product release servers even if the submitted keycorresponds to the prepurchase keys associated with the prepurchaseevent if the one or more of the consumers have not satisfied theprepurchase conditions.

In some embodiments, the prepurchase conditions comprise one or more ofsubmitting contact information, purchasing or subscribing to one or moreother products, spending a threshold amount of money and agreeing to aterms of use of the product. In some embodiments, the prepurchase dataincludes identification of all or a subset of one of sets of customercontact information of a plurality of accounts of an account database,further comprising, for each of the prepurchase events, transmitting theprepurchase key to network accessible locations identified by the subsetof the one of the sets of customer contact information with the productrelease servers. In some embodiments, the method further comprisesadding the contact information submitted to satisfy the prepurchaseconditions to the one of the sets of customer contact information of theaccount associated with the prepurchase event with the product releaseservers. In some embodiments, the method further comprises, for each ofthe prepurchase events, generating with the product release servers aprepurchase listing that identifies the product based on the metadata,the release date of the product and the starting time of the prepurchaseevent.

In some embodiments, the method further comprises generating one or moreprepurchase preorder keys and one or more prepurchase preorder eventswith the product release servers based on prepurchase preorder data forthe product indicated by the third party device, wherein the prepurchasepreorder data includes information that identifies one of theprepurchase events, for each of the prepurchase preorder events, withthe product release servers, facilitating ordering of the product by oneor more customers during the prepurchase preorder event if one or moreprepurchase preorder keys submitted by the customers correspond to theprepurchase preorder keys associated with the prepurchase preorder eventand preventing ordering of the product by the one or more customersduring the prepurchase preorder event if the one or more prepurchasepreorder keys submitted by the customers do not correspond to theprepurchase preorder keys associated with the prepurchase preorder eventand facilitating access to the product by the one or more customers thatordered the product during the identified one of the prepurchase eventswith the product release servers. In some embodiments, the product dataincludes a content file containing the product and the content filecomprises one or more of the group consisting of: a digital book, animage, a video, audio, a computer application.

A third aspect is directed to a non-transitory computer-readable mediumstoring a product release platform configured to generate a productlisting identifying a product based on product data received from athird party device, wherein the product data a product release date, andmetadata associated with the product; generate one or more prepurchasekeys and one or more prepurchase events based on prepurchase data forthe product indicated by the third party device, wherein the prepurchasedata includes a starting time, an end condition and pricing data foreach of the prepurchase events, wherein the starting time is before theproduct release date; and for each of the prepurchase events, facilitateaccess to the product to one or more customers during the prepurchaseevent if one or more keys submitted by the customers correspond to theprepurchase keys associated with the prepurchase event and prevent salesof the product to the one or more customers during the prepurchase eventif the one or more keys submitted by the customers do not correspond tothe prepurchase keys associated with the prepurchase event.

In some embodiments, each of the keys is included within a hyperlinkthat links to a page associated with the prepurchase event of that keyand submits the key to the product release platform for determining ifthe key corresponds to the prepurchase keys associated with theprepurchase event. In some embodiments, the end condition is one or moreof an end time, a quantity of sales, a maximum quantity of customersaccessing the prepurchase event, an inventory status of the product andmanual cancellation of the event, and further wherein, for each of theprepurchase events, upon reaching the end condition the product releaseplatform is operable to terminate the prepurchase event. In someembodiments, the pricing data is a pricing metric that indicates a pricevalue for the starting time and one or more subsequent times between thestarting time and an end of the prepurchase event as indicated by theend condition. In some embodiments, the prepurchase data includes one ormore prepurchase conditions, and further wherein, for each of theprepurchase events, the product release platform is operable to preventsales of the product to one or more of the consumers even if thesubmitted key corresponds to the prepurchase keys associated with theprepurchase event if the one or more of the consumers have not satisfiedthe prepurchase conditions.

In some embodiments, the prepurchase conditions comprise one or more ofsubmitting contact information, purchasing or subscribing to one or moreother products, spending a threshold amount of money and agreeing to aterms of use of the product. In some embodiments, the medium furthercomprises an account database stored on the non-transitorycomputer-readable medium, the account database including a plurality ofaccounts each having a set of customer contact information, and furtherwherein, for each of the prepurchase events, the prepurchase dataincludes identification of all or a subset of one of the sets ofcustomer contact information and the product release platform isoperable to transmit the prepurchase key to network accessible locationsidentified by the subset of the one of the sets of customer contactinformation. In some embodiments, the product release platform isoperable to add the contact information submitted to satisfy theprepurchase conditions to the one of the sets of customer contactinformation of the account associated with the prepurchase event. Insome embodiments, for each of the prepurchase events, the productrelease platform is operable to generate a prepurchase page thatidentifies the product based on the metadata, the release date of theproduct and the starting time of the prepurchase event.

In some embodiments, the product release platform is operable togenerate one or more prepurchase preorder keys and one or moreprepurchase preorder events based on prepurchase preorder data for theproduct indicated by the third party device, wherein the prepurchasepreorder data includes information that identifies one of theprepurchase events, for each of the prepurchase preorder events,facilitate ordering of the product by one or more customers during theprepurchase preorder event if one or more prepurchase preorder keyssubmitted by the customers correspond to the prepurchase preorder keysassociated with the prepurchase preorder event and prevent ordering ofthe product by the one or more customers during the prepurchase preorderevent if the one or more prepurchase preorder keys submitted by thecustomers do not correspond to the prepurchase preorder keys associatedwith the prepurchase preorder event and facilitate access to the productby the one or more customers that ordered the product during theidentified one of the prepurchase events. In some embodiments, theproduct data includes a content file containing the product and thecontent file comprises one or more of the group consisting of: a digitalbook, an image, a video, audio, a computer application.

A fourth aspect is directed to a product release system for enablingprepurchase of one or more products. The product release systemcomprises one or more servers including a processor and a non-transitorycomputer-readable medium coupled with the processor, storing a productrelease platform having a user interface and able to be communicativelycoupled with one or more third party devices over a network, wherein theproduct release platform is operable to generate a product listingidentifying a product based on product data received from a third partydevice, wherein the product data includes a product release date, andmetadata associated with the product, generate one or more prepurchaseevents based on prepurchase data for the product indicated by the thirdparty device, wherein the prepurchase data includes a starting time, anend condition and pricing data for each of the prepurchase events,wherein the starting time is before the product release date, for eachof the prepurchase events, enable the adjustment of the starting time,the end condition and the pricing data of the prepurchase event and foreach of the prepurchase events, facilitate access to the product to oneor more customers during the prepurchase event based on the prepurchasedata.

In some embodiments, the end condition is one or more of an end time, aquantity of sales, a maximum quantity of customers accessing theprepurchase event, an inventory status of the product and a manualcancellation of the event, and further wherein, for each of theprepurchase events, upon reaching the end condition the product releaseplatform is operable to terminate the prepurchase event. In someembodiments, the pricing data is a pricing metric that indicates a pricevalue for the starting time and one or more subsequent times between thestarting time and an end of the prepurchase event as indicated by theend condition. In some embodiments, the prepurchase data includes one ormore prepurchase conditions, and further wherein, for each of theprepurchase events, the product release platform is operable to preventsales of the product to one or more of the consumers if the one or moreof the consumers have not satisfied the prepurchase conditions. In someembodiments, the prepurchase conditions comprise one or more ofsubmitting contact information, purchasing or subscribing to one or moreother products, spending a threshold amount of money and agreeing to aterms of use of the product.

In some embodiments, for each of the prepurchase events, the productrelease platform is operable to generate a prepurchase page thatidentifies the product based on the metadata, the release date of theproduct and the starting time of the prepurchase event. In someembodiments, the product release platform is operable to generate one ormore prepurchase preorder events based on prepurchase preorder data forthe product indicated by the third party device, wherein the prepurchasepreorder data includes information that identifies one of theprepurchase events, for each of the prepurchase preorder events,facilitate ordering of the product by one or more customers during theprepurchase preorder event and facilitate the purchase of the product bythe one or more customers that ordered the product during the identifiedone of the prepurchase events. In some embodiments, the product dataincludes a content file containing the product and the content filecomprises one or more of the group consisting of: a digital book, animage, a video, audio, a computer application.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a product release system for providing features of aproduct release platform according to some embodiments.

FIG. 2 illustrates a block diagram of an exemplary computing deviceaccording to some embodiments.

FIG. 3 illustrates a prepurchase page according to some embodiments.

FIG. 4 illustrates an analytics page according to some embodiments.

FIG. 5 illustrates a method of enabling prepurchase of one or moreproducts via one or more product release servers according to someembodiments.

FIG. 6 illustrates a method of a customer device purchasing a productvia a prepurchase event according to some embodiments.

DETAILED DESCRIPTION OF THE INVENTION

The advent of ecommerce has created exciting opportunities for themillions of individuals and companies that bring new products to marketeach year. These products can be physical (e.g. paper books), digital(e.g. ebooks) or services (e.g. financial services). Herein, theseproducts and services that can be listed and sold or subscribed toonline are referred to as “products.”

Unlike “brick and mortar” retailers that can only stock a small numberof items per square foot of physical shelf space, thanks to ecommerce,online merchant shelf space is infinitely scalable at relatively lowcost, thereby enabling merchants to stock more products from a greaternumber of product creators.

Today, it's not uncommon for online merchants to stock tens of thousandsor even millions of items.

To support the influx of the millions of new products introduced eachyear, online merchants have developed sophisticated systems capable ofreceiving, processing, and publishing thousands of new product listingseach week. These systems are highly automated and efficient, for withoutsuch automation it would be economically unfeasible for online merchantsto open their virtual shelves to accommodate so many product creatorsand products.

The Limitation of the Conventional Product Release Date

When a new product is listed at an online merchant, one of the mostimportant pieces of metadata is the product release date, also commonlyreferred to as, “availability date,” “launch date,” “productintroduction date,” “public release date,” “drop date,” or “generalavailability date” among other similar phraseology. This product releasedate corresponds to the date at which the product was released at theonline merchant in the past, or the date at which a forthcoming newproduct will release and become purchasable in the future.

New products are exciting to consumers because these products embodyinnovations intended to satisfy unmet needs and desires of themarketplace. For many consumers, what's new and what's coming in thefuture is often more exciting than what was already introduced in thepast.

The consumer fixation on what's new creates special challenges forproduct creators. It means the product release date often marks the dateof peak consumer excitement and peak sales, after which consumerenthusiasm wanes in favor the next newer shiny object. It means manyproduct creators get only one chance to make their upcoming productlaunch a success.

Further compounding the product launch challenge for creators is thefact that a new product often appeals to different customer segments forcompletely different reasons. For example, for a young family with a newinfant, a new minivan represents a family transportation vehicle,whereas to an Uber driver, the same minivan represents how the driverwill carry out their transportation business. The van's safety featuresmight appeal most to the family, whereas the van's passenger and luggagecapacity might be most appealing to the Uber driver. A single releasedate therefore makes it difficult for product creators to plan andexecute marketing campaigns tailored to target various customersegments.

The conventional single release date also makes it difficult for productcreators to offer special loyalty incentives to various customersegments when all customers must wait to purchase, receive and/or access(in the case of subscription or rental services) the product on the samerelease date.

The Discoverability Challenge for New Products

The democratized access to online retail distribution is a mixedblessing for product creators. Although it means that product creatorsthat were previously denied access to physical retail distribution cannow gain ubiquitous access to online distribution, the unlimited shelfspace aspect of online merchants means that merchant catalogs can swellto millions or even hundreds of millions of items. This means thatdiscoverability is an increasingly difficult challenge for anyoneplanning to release a new product via ecommerce in the future. Each day,these virtual shelves become more crowded.

Product Creators Turn to Preorders to Raise Visibility of Upcoming NewProduct Launches

Preorders allow product creators to advertise upcoming new productreleases in online merchant listings in advance of the product's generalrelease date. When a customer preorders a product, they are placing apurchase order, much like a reservation, that will allow the customer toreceive the forthcoming product at a future date (or soon after itsofficial public release date). A preorder listing can raise thevisibility of upcoming product launches by enabling product creators andmerchants alike to market products to customers in advance of theproduct's availability.

For both product creators and online merchants, preorder listings makeit possible to capture customer order reservations in advance of theproduct's release date. By monitoring accumulated preorder counts,product producers and merchants can measure anticipated customer demandand make more informed resource allocation decisions about marketing,product manufacturing and inventory levels. For most physical anddigital products on preorder, a customer is typically not charged forthe product until the product's general release date arrives and theproduct begins shipping to the customer.

Preorder Limitations

Although preorders open up new opportunities for product creators andmerchants to market new products online, most customers do not takeadvantage of preorders, and this in turn means that most productcreators don't take advantage of preorders. The majority of customersopt instead to wait until after the product's general release datearrives to make their purchase. After all, as customer thinking goes,why should a consumer order a product weeks or months in advance only toreceive the product at the same time as everyone else, or when otherproducts can be purchased now to meet similar needs?

A New Method and System for Merchandising and Marketing New ProductReleases at Scale

Embodiments described herein disclose a system, method and devices thatgreatly expand the conventional temporal timeline for new productintroductions.

The system enables creators of physical and digital products, as well asother members of the product supply chain (e.g. merchants, anddistributors that supply merchants) that help product creators bringthese products to market via online merchants, to raise the visibilityand desirability of upcoming product releases, and to more effectivelytarget different customer segments with the same product. The systemenables online merchants to efficiently receive, process and publishthese product listings at scale. Further, by operating at scale thesystem enables more online merchants and product creators to takeadvantage of this new opportunity to market new products moreeffectively to customers.

FIG. 1 illustrates a product release system 100 for providing featuresof a product release platform 99 according to some embodiments. As shownin FIG. 1, the system 100 comprises one or more product release servers102, one or more product controller devices 104, one or more buyer orcustomer devices 106, a payment processing entity 110 and one or morethird party servers 112, all coupled together over one or more networks108. Alternatively, the third party servers 112 are able to be omitted.The networks 108 are able to be one or a combination of wired orwireless networks as are well known in the art. Although as shown inFIG. 1 one product release server 102 is coupled with two productcontroller devices 104, one third party server 112 and two customerdevices 106, it is understood that the system 100 is able to compriseany number of servers 102, product controller devices 104, third partyserver 112 and/or customer devices 106 coupled together via the network108. As used herein “product controller” is able to refer to any entityhaving control over a product including, but not limited to, productcreators (e.g. authors), merchants, suppliers and distributors.

The one or more product release servers 102 are able to store, maintainand/or operate a product release platform 99 for providing theprepurchase and other features described below. In some embodiments, theentirety of the product release platform 99 is able to be provided bythe product release servers 102. For example, the product releaseplatform 99 features are able to be provided in the form of one or morewebsites operated by the product release servers 102. Alternatively, auser is able to download some or all of the product release platform 99from the product release servers 102 onto one of the product controllerdevices 104, wherein the product release platform 99 is in the form of aprogram or application that is able to execute locally on the productcontroller device 104 and provides some or all of the platform features.In such embodiments, after being downloaded to the product controllerdevice 104, the application is able to use the local memory on theproduct controller device 104 to store and utilize data necessary foroperation of the application in an application database on the productcontroller device 104. Alternatively, some or all of the data foroperating the application is able to be stored in a server database onthe product release servers 102 such that the application must connectto the product release servers 102 over the networks 108 in order toutilize the data on the server database. For example, the locallyexecuting application is able to remotely communicate with the productrelease servers 102 over the network 108 to perform any features of theapplication and/or access any data on the server database not availablewith just the data on the application database. In some embodiments, thesame data is stored on both the server database and the applicationdatabase such that either local or remote data access is possible. Insuch embodiments, the databases are able to be periodically synchronizedover the network 108. Alternatively, the product release platform 99 isable to be in the form of a plugin that operates on top of the existingprogramming of one or a plurality of third party servers 112 and/orwebsites (e.g. to provide added functionality to a third party websiteoperated by the third party server 112).

In any case, in such embodiments the downloaded application, pluginand/or product release servers 102 together are able to provide all ofthe features of the product release platform 99 by communicating via thenetwork 108. In other words, together and/or separately the features ofthe product release platform 99 are able to be provided by one or moreplugins operating on other website/servers (e.g. servers 112), one ormore websites on the servers 102 and/or a local application on theproduct controller devices 104. Alternatively, the application and/orplugin is able to provide all of the features of the product releaseplatform 99 without the servers 102. Additionally, it should be notedthat, for the sake of brevity, the following discussion relates to thefunctions and operation of the product release platform 99 in the formof a website, user interface and/or database operating on the productrelease server 102, however it is understood that the discussion is ableto also relate to the function and operation of the application/plugin,the application/plugin user interface and the application/plugindatabase.

The third party servers 112 are able to be operated by merchants,aggregating entities (e.g. distributors), product creators operatingtheir own direct-to-customer merchant site and/or othernetwork-accessible software and/or hardware entities. Specifically, thethird party servers 112 are able to be entities that provide a websiteor application to distribute and/or facilitate purchase of, or access to(in the case of subscription and rental services) digital or physicalproducts and/or services. The product controller devices 104 andcustomer devices 106 are able to be any electronic device capable ofaccessing network accessible locations such as the product releaseserver 102, the third party servers 112 and/or the payment processingentity 110. The payment processing entity 110 is able to be a financialinstitution capable of executing financial transactions.

FIG. 2 illustrates a block diagram of an exemplary computing device 200according to some embodiments. The computing device 200 is able to beone or more of the servers 102, third party servers 112, productcontroller devices 104 and/or the customer devices 104. In general, ahardware structure suitable for implementing the computing device 200includes a network interface 202, a memory 204, a processor 206, I/Odevice(s) 208, a bus 210 and a storage device 212. Alternatively, one ormore of the illustrated components are able to be removed or substitutedfor other components well known in the art. The choice of processor isnot critical as long as a suitable processor with sufficient speed ischosen. The memory 204 is able to be any conventional computer memoryknown in the art. The storage device 212 is able to include a harddrive, solid state storage, network-attached storage, cloud storage,RAM, SRAM, CDROM, CDRW, DVD, DVDRW, flash memory card or any otherstorage device. The computing device 200 is able to include one or morenetwork interfaces 202. An example of a network interface includes anetwork card connected to an Ethernet or other type of LAN. The I/Odevice(s) 208 are able to include one or more of the following devicescapable of inputting or conveying data such as a keyboard, mouse,monitor, display, printer, scanner, modem, touchscreen, buttoninterface, speech recognition interface, and other devices.

The product release platform 99 software or module(s) 230 used tooperate the product release platform 99 (e.g. application, plugin and/orwebsite) are likely to be stored in the storage device 212 and memory204 and processed as applications are typically processed. More or lesscomponents shown in FIG. 2 are able to be included in the computingdevice 200. In some embodiments, platform hardware 220 is included.Although the computing device 200 in FIG. 2 includes software 230 andhardware 220 for the product release platform 99, the features of theproduct release platform 99 are able to be implemented on the computingdevice 200 in hardware, firmware, software or any combination thereof.Examples of suitable computing devices include a personal computer, alaptop computer, a computer workstation, a server, a datacenter, amainframe computer, a handheld computer, a personal digital assistant, acellular/mobile telephone, a smart appliance, a gaming console, adigital camera, a digital camcorder, a camera phone, an iPod®, a videoplayer, a DVD writer/player, a Blu-ray® writer/player, a television, ahome entertainment system or any other suitable computing deviceincluding any network-connected terminal with a screen connected toremote computing, I/O processing and data storage resources.

The Product Release Platform

The product release platform 99 enables product controllers to create,launch and manage custom prepurchase events. The product releaseplatform 99 (as implemented by the application, plugin and/or website)is able to comprise multiple enabling capabilities, organized andreferred to herein as modules. These modules can be implemented asdiscrete functional objects within a product release platform, or thefunctions of certain modules as described may be combined with othermodules or omitted. In some embodiments, the functions of one or more ofthe modules are accessible to users via a graphical user interface.Example modules of the product release platform 99 comprise a login andregistration module, a listing generation module, a vetting module, aprepurchase event module, prepurchase preorder module, a dashboardmodule, a purchase module, an analytics module, a coupon module, asubscriber module, an event bid module and an inventory module, whereinthe platform user interface is configured to enable users to utilize themodules.

The Login and Registration Module

The login and registration module enables a user to create an account onthe platform by inputting identification/contact information (e.g.username, password information, an email, passcodes, alternate contactmethods, biometrics, two-factor authentication using text, voice oremail and/or a security token) via the graphical user interface that isthen associated with the account such that the identification/contactinformation is able to be used to identify the user when logging ontothe platform. The identification/contact information associated with theaccount is able to be stored in an account database (e.g. on the servers102) or another network accessible location. Alternatively, the logininformation is able to be omitted and a user is able to use the platformwithout creating a user profile or logging in. In some embodiments, forunregistered customers who wish to purchase a product or serviceassociated with a prepurchase event, the account registration processcan be initiated in part—or fully integrated—within the shopping cartcheckout process.

After an account is created, the user is able to access the account andany data associated with the account by entering theidentification/contact information in order to identify themselves tothe platform. In particular, the data associated with the account isable to include one or more products, events associated with theproducts, data associated with the products and/or events (e.g. salesdata, sales analytics, pricing data, product metadata, event rules,event times), and/or a set of previously captured customer contact data(e.g. email addresses, telephone numbers, social media accounts). Thecustomer contact data is able to be associated with the accountgenerally, associated with one or more products associated with theaccount (e.g. products purchased by the users who the customer contactdata is from) and/or associated with one or more events associated withthe account. For example, customer contact data is able to be capturedby the product release platform through a prepurchase event (asdescribed below) and added to the data for the account associated withthat event. This data will then be recorded as associated with theevent, the product or service of the event, and the account that createdthe event. As a result, the owner of the event (e.g. product controller)is able to access and manipulate (e.g. copy, sort, filter, edit, add,delete, download) this data in order to use the data for research and/orgeneral marketing purposes.

In some embodiments, the state of the user when they visit the productrelease platform 99 is either logged in, or not logged in. If the uservisits the product release platform 99 in a logged in state, then theresources, capabilities and personalized features of the product releaseplatform are available to them without taking further action to log in.If a user visits the product release platform 99 and they are not loggedin, the module is able to provide the option to enter their emailaddress/password combination, or one or more of the alternateauthentication methods mentioned above, or provide the option to createan account via a graphic user interface that collects this information.

The Listing Generation Module

The listing generation module enables an account (e.g. associated withthe product controller) to generate a product listing on the productrelease platform 99 by inputting product data. As described below, thisproduct data is able to be used to generate a product listing as well asprepurchase and/or prepurchase preorder events. The product data is ableto comprise one or more of a general release date, a name/title,metadata about the product (e.g. description, product language,categorization, pricing, rating, or other characteristics of theproduct) and optionally the content file including the product itself(for digital products). For example, the metadata is able to include oneor more of a product name, product description, product categories,unique numeric or alphanumeric product identifiers (e.g. internationalstandard book number, barcodes, Universal Product Code (UPC),International European Article Number (EAN), a third party server 112issued identifier (e.g. merchant issued identifier), or any otherinstantiation of an identifier), the brand identity of the productcontroller, customer testimonials, customer reviews, release date,preorder date, prepurchase event start/end date(s), preorder start/enddate(s), images, photographs, illustrations, documentation of theproduct, language of the product, categorization, pricing, rating,inventory and fulfillment status, or other characteristics of theproduct.

The listing generation module is then able to generate a listing for theproduct based on the inputted product data (either with or without thecontent file). If the content file was included in the product data (orthe inventory and fulfillment readiness status is satisfactory in thecase of a physical product), the generated listing will be a completelisting. If the content file was not included (or the inventory andfulfillment readiness status is unsatisfactory in the case of a physicalproduct), the listing is still able to be generated, but the productwill not be able to be generally released/sold/accessed, or sold via aprepurchase event until the content file is added to the product datafor the listing or the inventory and fulfillment readiness status issatisfactory/made satisfactory (e.g. the product inventory is in placefor customer delivery per the unique rules and requirements that applyto the product). For example, if a product controller attempts togenerate a prepurchase event for a listing that does not have a contentfile (or lacks an acceptable inventory status), the prepurchasegeneration module is operative to prevent completion of the prepurchaseevent (e.g. publication of a prepurchase event page) and/orautomatically delay the start of the event until the content file hasbeen uploaded (or the product inventory has been delivered) and/orvetted (optionally including a buffer period). In particular, anauto-delay function of the product release platform 99 is able tomonitor upcoming events (e.g. dates of prepurchase events, preorderprepurchase events as described below, general release events) andautomatically delay the launch of those events if the content file hasnot been received (or the inventory and fulfillment readiness status forthe product is unsatisfactory) and/or product listing has not beenvetted before the start date of the events (e.g. including apredetermined buffer). In some embodiments, the auto-delay function isable to implement additional requirements that must be satisfied toprevent the auto-delay of the event.

The content file is able to comprise one or more of ebooks, computersoftware, downloadable applications, video games, audio, video, images(e.g. photographs, artwork), fonts, online courses, research reports,virtual goods and currencies used within virtual economies (e.g. withingames), templates, and/or other types of digitally deliverable and/oraccessible products. Additionally, the listing generation module is ableto receive and store the content file in a plurality of different fileformats so that these various options support various customer devicerequirements or preferences (e.g. in the case with ebooks, mobi, epuband PDF; with images, jpg, png, tiff; and with audio, MP3 and Way).

In performing the listing generation, the listing generation module isable to create a page (e.g. a webpage having a unique uniform resourcelocator (URL) and/or a page/screen in an application) operated by theproduct release platform 99 and dedicated to the product (e.g.describing the product and its availability date) and/or add the productto a product catalog of the platform (such that it is able to be foundby customers searching the catalog, pre-ordered and/or purchased via anassociated prepurchase event or a general release if the conditions aremet). Alternatively or in addition, the module is able to automaticallyformat and transmit the product data from one third party server 112 toone or more other third party servers 112 as a structured data feed(e.g. electronic data interchange (EDI) or other electronic delivery orupload method) such that the receiving third party servers 112 are ableto generate one or more product listings. In some embodiments, thestructured data feed comprises a prepurchase event activation date andtime (if one has been created as described below), a reference to thelocation of the inventory (or when the inventory will be delivered) andstatus, and the ability to update all this information via future EDIupdate feeds as things change (like if a product controller updatestheir product description, changes prepurchase event access or endconditions, experiences production delays, or delays or cancels aproduct release event). As a result, the listing module provides thebenefit of enabling third party servers 112 to use the product data tocreate and update standalone product listing pages, to add prepurchaseevent information to existing product listing pages, and/or tomerchandise the availability of these prepurchase events elsewhere intheir online stores so they can point customers to the prepurchaseevent's listing page(s).

The Vetting Module

The vetting module enables product release platform operators to ensurethat prepurchase events, prepurchase preorder events and productlistings are complete, accurate, and in compliance with policies (e.g.distributor or merchant policies entered into the system), or incompliance with applicable laws governing the sale or distribution ofsuch products. Specifically, as the product controller (e.g. via aproduct controller device 104) is interfacing with the listinggeneration module to create or modify a listing as described above, thevetting module is able to dynamically provide real time, on-screenalerts if it detects that the entered information is incomplete (e.g. aproduct description that's too short to meet stored requirements; or arequired data field that's not completed), disallowed (e.g. a productdescription that's too long; words, phrases, keywords, hyperlinks,personally identifiable information, categories or content that violatepolicies or applicable laws), or inaccurate. In doing so, the vettingmodule is able to automatically or partially automatically checksubmitted product data to determine if the data meets the requirementsof generating a complete listing, a prepurchase event, and/or aprepurchase preorder event for the product.

Alternatively or in addition, the vetting module is able to enable thesubsequent review of listings. In particular, the vetting module is ableto generate a page for human confirmation and/or automatically check ifthe product data does not violate listing requirements (e.g.requirements of the product release server 102 and/or a third partyserver 112). In some embodiments, the vetting module consolidatesreviewable listing elements of one or more product listings within asingle graphical user interface to allow multiple prepurchase events tobe reviewed at once. Additionally, if it is confirmed that an issuewould prevent or delay the activation of the event, whether due toerror, omission or policy violation, the module is able to (or enablesan operator to) flag the listing as requiring modification, enterhelpful written guidance to assist the product controller in repairingthe issue, and then convey that guidance to the product controllerautomatically via one or more communications methods including email,on-screen alerts, voice messaging and/or text message.

In some embodiments the product release platform 99 will not allow animproperly categorized product listing to be published. For example, theproduct release platform 99 would prevent a children's ebook from beingstocked, categorized and sold as a children's book if it in factcontains adult themes not suitable for children; or if the metadata isimproperly formed, like an incomplete or inadequate product description;or a merchandising image doesn't meet acceptable standards for such abook; or if the content is completely disallowed from being sold (likecertain taboo erotica, underage erotica, or illegal bomb-makinginstruction manuals). In some embodiments, on the product controller'sdashboard, the vetting module automatically highlights product listingsthat have been blocked for publication or distribution such that theproduct controllers are able to edit, repair or delete the listings asdesired. Alternatively, in some embodiments the vetting module is ableto be omitted.

The Prepurchase Event Module

The prepurchase event module enables an account (e.g. product controllerassociated with the account) to generate any number of prepurchaseevents for a product listing on the product release platform 99.Specifically, the module enables the product controller to generate anew product listing or identify an existing product listing from thelistings associated with the account (adding missing product data ifnecessary to complete the listing) and input prepurchase data to createa customized prepurchase event (for the listing/product) where acustomer is able to purchase the product before its general releasedate. The prepurchase data is able to include one or more of an eventstart time, event duration data, pricing data, permission data (e.g.rules defining how the event is accessed) and/or one or more prepurchaseconditions. This prepurchase data is able to be stored in a prepurchaseevent database for reference by the product release platform 99 tofacilitate the execution of the prepurchase event.

The duration is able to be a start date and/or time before the generalrelease date and optionally an ending condition. For example, the endingcondition is able to be an end date and/or time, a maximum quantity ofunits authorized for sale during the prepurchase event (e.g. for alimited prepurchase event), a maximum quantity of customers using a keyfor the event, a depletion of customer-fulfillable inventory (e.g. soldout or out of stock), the achievement of a sales goal, manualcancellation (e.g. by the account that controls the event) and/or otherparameters upon which the end of the duration is able to be determined.Alternatively, the end condition is able to be the general release dateby default. In some embodiments, for static dates the module enables theselection of the duration data via enabling selecting from apoint-and-click clickable calendar; entering a free form text such as“Sep. 23, 2020;” selecting or entering a total number of days (e.g. anumber of days from the start date) and/or via pull down menu optionswhere the product controllers choose the [month], [day], [year] or even[exact time down to the minute]. Alternatively or in addition, thestatic date selection is able to be received via voice commands wherethe product controller is prompted to provide a date.

For a manual cancellation, the module enables the account controllingthe event to manually input an “event termination” command that ends theprepurchase event at any time for any reason. In some embodiments, themodule enables the account to modify the end condition during the event.Alternatively, the module is able to prevent changes to one or morecharacteristics of the event (e.g. including the ending condition) oncethe event has begun. In some embodiments, to assist product controllers,the prepurchase event module is operative to display start and enddates/times in multiple time zones. Alternatively or in addition, theprepurchase event module enables the product controller/account toconfigure their prepurchase event listing to activate and/or terminateat different times and/or time zones or markets (e.g. multiple startdates/times and/or end conditions).

The pricing data is able to be static or dynamic. If the pricing data isa static price, the price will not change unless the account that ownsthe event manually changes it during the event. If the pricing data is adynamic price it is able to change during the event based on one or morefactors. Specifically, the pricing data is able to be a price metricthat indicates how the price changes based on the one or more factorssuch as time (e.g. current date, a specific data after the start datebut before the end date/condition, time left in the prepurchase event,time since last sale of the product within the event), current quantityof units of the product sold during the event, current amount of incomegenerated from the event and/or current quantity of transactions orcustomers during the event.

For example, the prepurchase event module is able to incrementallyincrease or decrease the price based on one or a combination of thefactors indicated by the price metric (e.g. the number of days since theevent began or the number of days until the general release:price=$20+$1 for each day since the event began; or the number of unitsremaining: price=$20+$30*((the initial number of units−the number ofunits remaining)/the initial number of units). Alternatively, thepricing data is able to be a fixed price (e.g. $5; $0, etc.); auctionpricing; subscription pricing; customer-sets-their-price; renting; downpayment deposits; and/or installment payments. Additionally, the pricedetermined by the pricing data is able to be dynamically adjusted by oneor more prepurchase conditions as described below. For example, avariable percentage discount is able to be applied to the price asdetermined by the pricing data if one or more conditions are met by thecustomer. For example, as described below, in some embodiments if thecustomer agrees to share their contact information with the productcontroller/account, or join a private mailing list, or take some otheraction, the customer may receive a predetermined discount on theprepurchase (as indicated in the pricing data).

The one or more prepurchase conditions are able to be one or moreactions that a customer must/may perform in order to prepurchase theproduct, adjust the price of the product and/or receive other benefitsfrom the product release platform 99. In particular, the prepurchaseevent module enables the product controller to condition a benefit onthe customer actions such as, but not limited to: the customeraffirmatively agreeing to a set of terms (e.g. selecting an agreementcommand), purchasing one or more other products, the transaction totalmeeting a price threshold, submission of a contact email (e.g. to bestored and associated with the account of the prepurchase event),agreeing to sign up for a mailing list, preordering one or more otherproducts, subscription to a group (e.g. a Facebook group), subscriptionto a service, watching a video, reading a text, completing a set ofquestions (e.g. a test or poll), promoting a message on social media,donating to charity, submission of desired contact data (e.g. telephonenumber, mailing address), completing a survey, agreement to a terms ofuse statement (e.g. agreeing to an anti-piracy promise prior toprepurchasing a digital product, agreeing to a confidentially pledge, orthe prospective customer asserting they are of an appropriate age orexperience level to purchase and responsibly use the product or service,digitally signing a release form or acknowledgement form, or agreeing touse the product in a responsible or safe or legal or recommended manner,or the prospective customer agreeing to hold the product controllerharmless), agreeing to leave a review of the product and/or otheractions/submissions/agreements. For example, the product controller isable to use the prepurchase event module to specify that in order topurchase the product of the prepurchase event the customer must havepreordered the product (e.g. for the prepurchase event and/or for thegeneral release date). Possible benefits are able to include one or moreof the ability to: gain access to view the prepurchase event, purchasethe product during the prepurchase event, gain access to one or morefuture prepurchase events, receive a discount on the product price, gainmembership to a subscriber email list, other types benefits and/or acombination thereof. Thus, the condition data of the prepurchase eventmodule provides the benefit of allowing the product controller greaterflexibility to configure their prepurchase event access and promotion toachieve maximum business benefit or some other non-business goal ofimportance to the product controller or product release platformoperator.

The permission data is able to be identification of one or moreprospective customers that are authorized to access the prepurchaseevent. For example, the prepurchase event module enables a productcontroller to specify that the prepurchase event is private and themodule will generate one or more digital keys that are required duringthe event in order to access the prepurchase event page and/or tocomplete the purchase of the product via the page. Specifically, themodule is able to generate, present and/or transmit the one or moredigital keys to the product controller for copying and distribution(e.g. to prospective customers). Alternatively or in addition, asdescribed below, the module is able to distribute the keys automaticallyto destinations or customers identified by the product controller. Thus,this private prepurchase event is visible only to those who haveknowledge of the prepurchase event and who possess the necessary digitalkeys.

The digital keys are able to comprise one or more of: codes, tokens,hyperlinks, passwords, pass phrases, and/or authorized affinityrelationship gateway identifiers, such as, making the prepurchase eventavailable only to customers who have a relationship with a credit cardcompany or affiliated business partner, or who are already a subscriberto a private mailing list or fan club to access the prepurchase event.The private prepurchase event is able to be transacted over a private“landing page” (e.g. landing page, webpage, application screen/page,graphical user interface) that is able to look different from thepublicly visible product listing page (e.g. that describes the generalrelease date), or may be available via a different hyperlink or networkaccessible location (e.g. URL or specific screen within an application)than the publicly visible product listing page. The private prepurchaseevent landing page is able to primarily focus on closing the sale androuting the prospective customer to the purchase action or shoppingcart. In some embodiments, for a private prepurchase event implementedon the product release server 102 and/or a third party server's 112(e.g. online merchant) product listing page, the private prepurchaseevent is able to be “unlocked” by the use of a cookie (as the key)deposited by the prepurchase event module in the prospective customer'sweb browser when they clicked on a hyperlink (generated by theprepurchase event module) such that the now “cookied” browser unlocksaccess to the private prepurchase event from the main product listingpage, and/or reroutes the customer to the prepurchase event page orlisting (as described below); or the product listing page is able topresent an option for a customer to manually enter a prepurchase eventkey; or when the customer performed some other activity prior tounlocking the prepurchase event.

The type of digital keys generated by the prepurchase event generationmodule for private prepurchase events is able to be selected for eachevent. In particular, the module enables one or more different key typesto be selected from the group comprising: a random code, a password, apass phrase, a captcha, a hyperlink including an embedded unique code,an unknown hyperlink URL, a token, web browser cookie and/or other typesof digital keys. In some embodiments, the digital keys are able to beone-time use codes either manually input or embedded in a hyperlink orcookie so that each key (e.g. one-time use code) is only able to be usedonce to access the prepurchase event, and after successful purchase therelevant key would expire, thereby rendering the key (and hyperlinksembedding it) unusable to future customers. This would have the benefitof preventing customers from sharing their private access credentialswith friends or on social media if such sharing is not desired by theproduct controller. In some embodiments, the prepurchase event module isable to enable the product controller to access existing customercontact information (associated with the product controller's account)previously captured or stored within the product release server 102,and/or upload new customer contact information via a uploaded file (e.g.format such as xls, txt, comma delimited, tab delimited) and/orpredetermined EDI method, or manually enter an unlimited number ofcustomer email addresses. The product release platform 99 is able to usethis data to generate the same number of keys (e.g. unique codes) tiedto the contact information of each prospective customer, and these keysare able to be shared by the product controller to each prospectivecustomer. As described above, these keys (e.g. codes and code-embeddedhyperlinks) are able to be made to be one-time-use only, limited use, orcould be unlimited use for instances where the product controller wantsto encourage or incentivize prospective customers to share the keys inexchange for goodwill, gifts, rewards, affiliate sales earnings, orother recognition.

For example, the prepurchase event module is able to generate ahyperlink that combines both a digital product identifier and an accesscode (e.g. https://musicprepurchaseplatform.com/942864/EWRP9K).Specifically, the hyperlink is able to include a randomly generated code(e.g. beginning with “EWR” or any other alphanumeric characters) andwhere “942864” is able to be any alphanumeric characters correspondingto one or more product identifiers (ID) attached to this product by theproduct release platform 99. Thus, the hyperlink is able to use theproduct identifier within the link to navigate to the desiredprepurchase event and then automatically submit the code to theprepurchase event module in order to allow the customer device 106 togain access to the event page and/or to gain access to the purchasefunction of the page. Alternatively or in addition, the productidentifier and an access token are able to be combined into a singlealphanumeric passcode that the prospective customer can manually enterinto the platform 99 to gain access to the prepurchase event.

In addition, for generated keys linked to the identity of a customer,from either the combined event code, product identifier or any key, theproduct release platform 99 is able to identify the account that createdthe prepurchase event and/or the identity of a customer as participatingin an affiliate program for which either or both parties (customerand/or product controller) are incentivized to share this unique codewith other prospective customers, even in the event of a privateprepurchase event, for the purpose of incentivizing the customer toshare the code or link within their social or marketing circles.

In some embodiments, the prepurchase event module is able to generatefor the product controller keys in the form of multiple (or an unlimitednumber of) one-time-use codes or tokens, or metered codes or tokens(e.g. authorizing a limited number of redemptions for each individualcode before it expires) so that each code is able to be used to accessthe prepurchase event a predetermined number of times as selected by theprepurchase event owner. Specifically, after successful purchase of theproduct using the relevant code or token, and/or after the code or tokenhas reached its allowable number of redemptions, the token is marked as“expired” and therefore invalid by the platform such that it cannot beused again. This prevents customers from sharing their private accesscodes with friends or on social media in instances where the prepurchaseevent owner desires to limit access to the event.

In some embodiments, similar to above, the prepurchase event generationmodule is able to enable the product controller to select, upload orenter customer contact information (e.g. email addresses or phonenumbers for texting) and the product release platform 99 is able to usethis data to automatically generate on demand, on a self-serve basis,the same number of unique codes attached to each customer contactinformation (and/or contact method), and then dispense these codes tothe product controller who would manage their disbursement. In otherwords, the module is able to generate a code document including thedesired number of code (and/or hyperlinks) that the product controlleris able to download or copy in order to distribute as desired. Similarto above, these codes could be made to be one-time-use only, or metered(as described above) or could be unlimited use for instances where theproduct controller wants to encourage and incentivize customers to sharethe code, possibly in exchange for goodwill, gifts, rewards, affiliatesales earnings, or other recognition. In any case, by tracking theredemption and authentication of the keys, the product release platform99 is able to track and report sales and/or key use back to the productcontroller (e.g. via the analytics module described below).

In some embodiments, the prepurchase event generation module furtherincludes an advertisement and/or key distribution function thattransmits information about the prepurchase event and/or the key(s) forthe event to one or more selected customers. Specifically, during orafter the prepurchase event generation process, the prepurchase eventmodule enables the prepurchase event creator to select the contactinformation of one or more customers from a list of customer contactinformation (e.g. email addresses, telephone numbers or other)associated with the product controller's account profile on the productrelease server 99, wherein the prepurchase event module is able to thenautomatically send an advertisement and/or key(s) for the event to theselected customers at the indicated contact points (identified by thecontact information). For example, the module is able to generate andtransmit via email, text or online screen messaging a link to theprepurchase event to the selected customers. In particular, in someembodiments the link is able to include the key for accessing/purchasingthe product during the prepurchase event. Alternatively, the prepurchaseevent creator is able to download or otherwise use the contactinformation to personally contact the customers as desired.

As another example, this message is able to be directed to customers ofthe product release server 102 and/or a third party server 112 (e.g. anonline merchant) that previously purchased products or services from theprepurchase event owner, and/or customers of the product release server102 and/or a third party server 112 that have purchased, viewed orexpressed interest in products similar to those of the prepurchase eventowner. In the case of a third party server 112, the contact informationis able to be transmitted from the third party server 112 to the productrelease server 102. The method of alerting customers about theprepurchase event is able to comprise one or more of an email alert, atext alert, an audio alert, a web page, a smart speaker device, visualpromotion of the prepurchase event or the product participating in theprepurchase event within the product release server 102 and/or a thirdparty server 112 customer-facing merchandising features (e.g. if theprepurchase event relates to a new hiking boot from brand A, and aprospective customer of the product release server 102 and/or a thirdparty server 112 catalog previously purchased a hiking boot from brandB, and/or the customer is browsing the hiking boot category, and/or theprospective customer is using search terms related to the topic ofhiking or hiking boots or other similar outdoor activities, then theproduct release server 102 and/or a third party server 112 can displayor advertise the availability of a prepurchase event to that specificcustomer). An additional related embodiment includes the product releaseserver 102 and/or a third party server 112 advertising a plurality ofproducts currently available to customers as a prepurchase. Anadditional related embodiment includes the product release server 102and/or a third party server 112 offering paid advertising opportunitiesto the product controller that created the prepurchase event, in whichthe advertising would be able to be displayed via one or more of thefollowing targeting options: prior customers of the product controller,customers of similar brands or products, customers that fit certaineducation, geographic, age, gender, income level, political orientationof other demographically targetable characteristics known by the productrelease server 102 and/or a third party server 112 about theircustomers, customers searching on specific search terms or browsingother products either similar to or complementary to the productcontroller's product, or a general audience.

Additionally, as described below with respect to the dashboard module,the product release platform 99 also enables product controllers whocreated the prepurchase event to download, add, delete and edit thecustomer contact information associated with their accounts.Alternatively, in some embodiments the seller is able to specify thatthe prepurchase event or the prepurchase preorder event (as describedbelow) is public such that generation of keys is unnecessary. In someembodiments, the prepurchase event module enables the product controllerwho created a prepurchase event to change the event from private topublic or from public to private at any time during the event.

If the product controller indicates in the permission data that theprepurchase event is to be public, the module is able to omit thegeneration and/or transmission of the keys. Although a publicprepurchase event is able to be visible to all customers of the productrelease server 102 and/or a third party server 112, it's still possiblethat the public prepurchase event is only exclusively available at theproduct release server 102 and/or a third party server 112, or a limitedplurality of the product release server 102 and/or third party servers112, or available for only a limited time at the product release server102 and/or a third party servers 112, or available on a prepurchaseevent page that is only visible to those who know the URL. A publicprepurchase event, when merchandised at the product release server 102and/or a third party server 112, is able to be accompanied by thepresentation of two or more event dates (the public release date and oneor more public prepurchase event dates). Specifically, at the productrelease server 102 and/or a third party server's 112, both or neither ofthe release date events may appear on the prepurchase event page and/orthe product listing page (e.g. the product release server 102 and/or athird party server 112 may simply decide to omit references to dates,and instead present the prepurchase event as a prepurchase event pagewhere product availability is presented as “available now,” or words tothat effect, and/or there may be no other indicator that the product isavailable now other than presence of a purchase button). The prepurchaseevent page is able to be designed to merchandise the prepurchase eventand direct the consumer into the shopping cart facility. Alternatively,the public prepurchase event is able to be merchandised directly on theproduct listing page of the product in the product release server 102and/or a third party server's 112 catalog.

In some embodiments as described above, during or after the prepurchaseevent creation process, the vetting module is able to check the valuessubmitted by the user to ensure they meet the requirements of creating aprepurchase event. For example, the module is able to flag or rejectsubmitted information that is erroneous or unacceptable (e.g. aprepurchase start time/duration must be earlier than a general releasedate of the product; price must be greater than or equal to zero) or anassociated product listing that is not complete (e.g. the content filehas not yet been uploaded and/or vetted; or physical product inventorystatus is insufficient to enable customer deliveries). In other words,the module is able to either automatically prevent generation of theprepurchase event at all and/or able to prevent or delay activation ofthe prepurchase event if the event has errors that have not beencorrected before the event start date (and/or a predetermined buffertime). Prepurchase events, prior to enabling customer purchases,generally require that the product controller has delivered thenecessary product inventory to the product release server 102 and/or athird party server 112 so that the product can be fulfilled (delivered)to the customer who orders the product following the start of theprepurchase event. This product inventory comes in the form of a digitalcontent file in the case of digital products, or physical inventory.This status information for digital and physical products is tracked bythe Inventory Module.

In some embodiments, the prepurchase event module is able to check aninventory status for the product and either automatically preventgeneration of the prepurchase event at all and/or prevent/delayexecution of the prepurchase event if the inventory status does not meeta required criteria. For example, to ensure the prepurchase event isready for activation and product fulfillment, the listing generationmodule is able to track inventory levels and locations of ready-to-shipproduct within customer fulfillment centers (e.g. warehousingfacilities, distribution centers, physical pickup locations), trackAdvance Shipment Notifications (ASNs), and reflect generalized inventorystatus (e.g. if the product is currently available for customer deliveryor not, and if so, knowledge of what quantities) on the prepurchaseevent listing pages.

In some embodiments, where the prepurchase event module enables theevent to be generated even with errors or without a content file, theprepurchase event module is able to email a product controller or flagsubmitted prepurchase events on the product controller's (that createdthe event) dashboard to notify them of errors that need to be correctedin order to prevent the event from being automatically delayed and/orcanceled. Additionally, using the dashboard module described below, theproduct controller is able to modify details of their prepurchase event,such as the ability to complete missing elements, or edit, delete, orotherwise modify prepurchase events.

Finally, once all of the required data is received by the prepurchaseevent generation module, the module is able to generate a prepurchaseevent listing or page that enables a customer to purchase the productbefore the general release date if they meet the required conditionsand/or possess the required key for the prepurchase event (if a key isrequired). In some embodiments, the prepurchase event page cannot befound/navigated to without the hyperlink generated by the prepurchaseevent module for the event. Alternatively, the page can be navigated toby a prospective customer, but the purchase feature cannot be usedwithout submission of the required key for the event (if any). In someembodiments, the prepurchase event page is linked to by the productlisting page of the associated product. In some embodiments, the eventpage comprises one or more of a countdown clock (indicating how longuntil the event ends), a plurality of release dates (e.g. including theprepurchase event duration and the general release date) and/or pricingdata (e.g. a static price associated with each release date; a currentdynamic price; and/or a pricing metric for the prepurchase event). Forexample, as shown in FIG. 3 the prepurchase page is able to display ageneral release time and/or date and one or more prepurchase event timesand/or dates (e.g. along with a countdown clock) and other data aboutthe product and the details of those events (e.g. duration, price,conditions). This dynamic countdown clock captures the time-limitedopportunity and urgency for the prospective customer to take advantageof the early prepurchase event. As described herein, “page” is able torefer to a webpage, a website, some or all of a program or applicationor other network accessible location.

As a result, the prepurchase event module provides the benefit ofenabling a product controller to customize a prepurchase event andthereby exercise greater control over the sales and marketing of theirproduct. Further, the option to create a plurality of prepurchase eventsopens up new marketing opportunities for product controllers. Forexample, the product controller may desire to create three separateprepurchase events, each running simultaneously or separated by somenumber of days so that they are able to run targeted prepurchasemarketing campaigns to different customer segments. For the earliestprepurchase event, the price might be higher or lower (or the same), orthe product controller may want to limit (meter) the number of peopleallowed to access that earliest prepurchase event, or they may want tooffer the earliest prepurchase event only to a subset of selectedcustomers, such as to subscribers to their private customer mailinglist, or to members of a loyalty reward club. A plurality of prepurchaseevents opens up myriad permutations for product controllers to buildcustomer excitement, reward customer loyalty, target unique customersegments with different marketing messages or campaigns, perform ABtesting of various marketing messaging or tactics, and to encouragecustomer behaviors that are advantageous to the product controller (suchas prepurchase event conditions of purchasing other products to unlockthe prepurchase event; agreeing to specific Terms of Use statements; orperforming other tasks such as signing up for a newsletter, sharingsomething on social media, or other tasks as a condition to unlockingthe prepurchase event).

The Prepurchase Preorder Module

The prepurchase preorder module enables product controllers to generatea prepurchase preorder event for a prepurchase event of a productlisting. As a result, the prepurchase preorder module enables customersto place a reservation for a product of an upcoming prepurchase event sothat at the time that the prepurchase event begins to accept customerorders, the customer's prepurchase preorder is automatically executedand the product fulfillment process is initiated. The benefit forproduct controllers is that they can begin marketing their prepurchaseevent weeks or months in advance, and the benefit for customers is thatthey can reserve the opportunity to purchase and receive an upcoming newproduct before the general public, rather than waiting for the startdate of prepurchase event before they can place their order.

To generate a prepurchase preorder event, the prepurchase preordermodule enables an account (e.g. product controller) to identify anexisting prepurchase event and submit a date and/or duration of when theprepurchase preorder event should begin (and end) and the module is ableto automatically generate a prepurchase preorder page (e.g. webpage,application page, preorder functionality on another page) for theprepurchase preorder event. The prepurchase preorder page is able toindicate the product (similar to the product listing page and/orprepurchase event page) and/or provide the ability to preorder theproduct for the prepurchase event. In some embodiments, one or more ofthe listing page, prepurchase event page and/or prepurchase preorderevent page are able to be combined. Further, the prepurchase eventand/or prepurchase preorder event information is able to be added to theplatform catalog (e.g. for customer merchandising).

In some embodiments, like the product listings described above, themodule enables the generation of the prepurchase preorder event beforethe prepurchase event has been finalized (e.g. before all of therequirements described above for the prepurchase event have beensatisfied). In other words, the module allows product controllers tocreate and launch prepurchase preorder events (i.e. begin acceptingcustomer preorder reservations) before the customer-fulfillable productinventory is received by the product release server 102 and/or a thirdparty server 112, since such product inventory isn't due to the productrelease server 102 and/or a third party server 112 until some timeperiod (defined by the product release server 102 and/or a third partyserver 112) in advance of the prepurchase event start date. Theprepurchase event start date is the date at which the product releaseserver 102 and/or a third party server 112 generally accepts customerpayment and is obligated to initiate customer delivery of the preorderedproduct.

In such embodiments, the prepurchase event module is able to require theproduct controller creating a prepurchase preorder event of anincomplete prepurchase event to affirmatively agree to complete theprepurchase event (e.g. meet the requirements of the prepurchase eventmodule described above) before the specified deadline. In suchembodiments, the preorder prepurchase module is able to automaticallysend reminder messages (e.g. text messages, popup messages, telephonicmessages, emails, selectable on-screen acknowledgment boxes, and/orother type of messages) to the product controller/account that createdthe prepurchase preorder event indicating that the prepurchase event isnot complete and/or needs to be complete by the deadline. In suchembodiments, the prepurchase preorder module is able to begin acceptingcustomer preorders (if the start time of the prepurchase preorder eventis reached) despite the prepurchase event not being finalized. Also insuch embodiments, the prepurchase preorder event is able to beautomatically cancelled, extended or delayed by the module if theassociated prepurchase event is canceled, extended or delayed (e.g. bynot completing the prepurchase event generation/activation as describedabove before a specified deadline). Alternatively, the prepurchasepreorder event is only able to be generated after the prepurchase eventhas been finalized. Additionally, like the prepurchase event generationmodule and vetting module described above, the prepurchase preorderevent module is able to dynamically or otherwise flag submitted errorsand is able to notify the product controller that the errors need to becorrected before the event is able to be generated.

Once the prepurchase preorder event has been generated, the prepurchasepreorder module enables customers to select one or more product/productlistings that have upcoming prepurchase events, and preorder thoseproducts for those events using the prepurchase preorder event. Forexample, the module is able to add a prepurchase preorder function tothe listing for the product (e.g. within the product catalog) and/or tothe prepurchase event page for the product and/or provide access to theprepurchase preorder page for the product. Specifically, the customer isable to submit their (future or current) payment and deliveryinformation (if not already captured by the platform 99) along with theselected products and the prepurchase preorder module will generate aprepurchase preorder reservation that is stored and associated with thecustomer's account. As a result, when the prepurchase event begins (i.e.the product is able to be prepurchased) the prepurchase preorder moduleis able to automatically (or upon confirmation from the customer)complete the purchase transaction and initiate delivery of the productto the customer. Additionally, in some embodiments if the prepurchaseevent requires submission of a key (e.g. the prepurchase event isprivate), the prepurchase preorder module is able to require submissionand verification of the key (in the same manner as described above withthe prepurchase event generation module) before the customer ispermitted to create the prepurchase preorder reservation.

As a result, the product release system 100 provides the advantage ofenabling product controllers to create one or more customized preorderevents for each of the prepurchase events in order to further enhancethe control they have over the marketing and distribution of their newproduct introductions. With a preorder of a product of a prepurchaseevent, a customer can view a product listing for an upcoming prepurchaseevent, and preorder the product of said prepurchase event, and theirpayment information is able to not be charged until the product isreleased to them on the special prepurchase event start date, whichmeans the customer fulfillment date is earlier than the general releasedate.

The Dashboard Module

The dashboard module enables product controllers to access the productlistings, prepurchase events, preorder prepurchase events, customer dataand other data associated with their account in order to view (e.g.preview as they are to be displayed), edit, modify, correct, complete,delete, reactivate and/or add to them. For example, the productcontrollers of are able to access their account's listings, prepurchaseevents and/or prepurchase preorder events associated with that accountthat are active, pending approval, expired, and/or in draft form. Asdescribed above, the dashboard is able to provide flags or other typesof notifications to alert product controllers of incomplete orincorrectly submitted listings and/or events, forthcoming productdelivery deadlines (e.g. for prepurchase events and/or prepurchasepreorder events), as well as enable the product controllers to correctand/or complete those pending items.

For example, a product controller is able to use the dashboard module tonavigate to a prepurchase event's configuration data to change the time,price or any of the other characteristics of the event (describedabove), or to check inventory status. These tools enable the productcontroller to modify many aspects of their prepurchase event, such asprepurchase event date, product description, rules for access(conditions), rules for discounts (e.g. coupons and conditional offers)or to create multiple prepurchase events (e.g. subject to the rules setby an online merchant, distributor or other entity). Additionally, thedashboard module is able to display active and expired events, thestatus of each, performance metrics related to each, and other data inaddition to enabling their modification. Similarly, in some embodimentsthe dashboard module is able to display and/or enable the download ofthe customer contact data and/or other data associated with the accountsuch that a product controller is able to use the data to directlycontact their customers or fans. Alternatively or in addition, themodule enables a seller to export customer contact information in one ormore structured formats so that this data may be easily integrated withthird party email marketing tools and/or customer relationshipmanagement systems (e.g. over the network 108).

The ability for a product controller, on a self-serve basis, to directlyedit how their product listing will appear in the product release server102 and/or a third party server's 112 catalog—and be made viewable byprospective customers—provides for the scalable enablement of thethousands of new product introductions which product controllers willdesire to list as prepurchase events and prepurchase preorder events.With a flood of dynamic, ever-changing product listings it is otherwisephysically, economically and practically unfeasible for an onlinemerchant to manage this data entry without the self-serve assistance ofthe product controller, and this facility is enabled by providingproduct controllers access to the dashboard module offering theseself-serve tools.

The Purchase Module

The purchase module enables a customer to select a product or servicefrom the product release platform 99 (e.g. via the catalog listingsand/or a prepurchase event page), submit payment information (if notalready known), and payment authorization. The purchase module processesthe transaction (e.g. via a payment processor), records the transactionin the databases for the accounts of both the customer and the productcontroller and initiates delivery of the product to the customer (e.g.makes the product deliverable to, or downloadable by, or accessible to,the customer's device 106, to the user's account/library on the productrelease platform 99 for future access, and/or to another networkaccessible location; initiates shipment of the product to customers). Ifthe product is being purchased via a private prepurchase event (orpreorder thereof), the module is able to verify that the customer haspresented a key for the event that matches one of the valid keysassociated with the event, and if not prevent the preorder or sale ofthe product. In some embodiments, each time a customer purchases aproduct via a prepurchase event or reserves the product as part of aprepurchase preorder event, the module transmits the customer anautomated confirmation message (e.g. text message, telephone message,email, message via a smart speaker device) with access informationand/or delivery information for their product, and such information mayinclude hyperlinks to product listing pages.

In one embodiment, for the product release server 102 and/or a thirdparty server 112 operating subscription services, where customers pay asubscription fee to access a large catalog of content, the module isable to release products to subscribers of a particular subscriptionservice before the product's general release date, wherein the productis able to be included at no extra cost to the subscriber as part theirsubscription (e.g. a new ebook released early to subscribers of an ebooksubscription service, or a new music album released early to subscribersof a particular streaming music service). In other words, just as theprepurchase module allows customers to purchase and receive a productbefore the general public release date, the prepurchase module alsoenables product controllers to utilize subscription services to makeproducts accessible to their subscribers earlier than the generalrelease date. Alternatively or in addition, the subscription servicecould charge subscribers an additional fee as the condition foraccessing such content earlier than the general public.

In some embodiments, the module enables product controllers to configurecustom “thank you” messages, utilizing one or more the customer'spreferred contact methods, which are able to be inserted into thepurchase confirmations transmitted by the purchase module. In theseembodiments, these purchase confirmations are able to also includeadvertisements for related products from this or other productcontrollers, or contain gifts, incentives or digital coupons. Suchpersonalized and customizable messages enable the product controller tocommunicate directly with the customer, even in situations where thecustomer identity and customer contact information is unknown to theproduct controller.

The Analytics Module

The analytics module enables a product controller to access account data(e.g. customer data, event data, sales data, product data, time-seriesdata) and download or otherwise manipulate the data for identifyingtrends, correcting mistakes and/or using the data to improve theirproduct sales and marketing. Further, in some embodiments the analyticsmodule is able to transmit alerts to the product controller, via acommunications method selected by the product controller (e.g. emailand/or text and/or voice and/or on-screen messages) each time they makea sale of their product, or on some predetermined frequency, and/orprovide via a graphical user interface visual “Daily Sales” charts whereproduct controllers are able to view their recent sales data ingraphical time-series form. Such daily sales charts are able toaggregate prepurchase sales data and prepurchase preorder reservationsfrom across multiple sales outlets as shown in FIG. 4, and/or integratethis data into existing sales reports for other products not onprepurchase or prepurchase preorder.

The Coupon Module

The coupon module is able to enable product controllers to generatecustom coupons that are able to be applied by the purchase module when acustomer uses the coupons to purchase or reserve the products associatedwith the coupons. In some embodiments, the purchase module is able tovalidate a coupon code entered directly into a digital shopping cartprior to consummating the purchase. This coupon code is able to beseparate from a prepurchase event key as well as any other incentivesattached to the prepurchase event key. In some embodiments, generatedcoupons are able to comprise a fixed price coupon, wherein the moduleenables the sellers to configure, on a self-serve basis, custom couponcodes that set a specific price or discount level, or any percentage-offlevel. In some embodiments, these coupons are able to be configured toexpire at a future date, including dates that may precede the end of theprepurchase or prepurchase preorder event. In this way, a seller is ableto advertise their prepurchase, or their prepurchase preorder, withwords to effect of, “25% off the regular price, available exclusively toprepurchase customers, good for the next three days only.” In someembodiments, the generated coupons are able to comprise a metered (i.e.limited redemption) coupon wherein the coupon module is able to generatea coupon code that will automatically expire after a predeterminednumber of redemptions as determined by the product controller. In suchembodiments involving a metered prepurchase event, a product controlleris able to advertise words to the effect of, “The exclusive prepurchaseevent is available only to the first 15,000 fans, after which theprepurchase event expires and you'll need to wait until the generalrelease in two weeks to purchase the product.” Additionally, the meteredcoupon is able to be combined with the fixed price coupon to createmyriad useful promotional permutations that the product controller isable to use concurrently, or in combination, or in sequence in advanceof the general release date.

In some embodiments, the generated coupons are able to comprise productfamily coupons, wherein if the seller produces multiple products, themodule is able to generate a single coupon code that customers are ableto apply to any one or plurality of products that are sold by theproduct controller at the product release server 102 and/or a thirdparty server 112. In some embodiments, the coupons are able to compriseone-time use coupons wherein the coupon module would enable productcontrollers, on a self-serve basis, to request one or more one-time usecoupons that the product controller is able to then use in theirmarketing promotions. Such coupons are useful for sellers who want toprint them on scratch-off cards, print them on business cards ormarketing literature, or dole them out selectively to customers ormarketing partners. In some embodiments, generated one-time-use couponsare able to be attached to the identity of the individual customer orcustomer group, useable by only said authorized customer or customergroup.

In some embodiments, the coupon module is able to integrate knowledge ofone of the above coupon methods directly into the prepurchase eventkeys. In this way, using the keys (e.g. with a single click on ahyperlink, or by manually entering a passcode), the product releaseplatform 99 is able to automatically recognize the identity of thecustomer, the product controller that created the prepurchase event, thecustomer's access credentials, and can automatically apply the couponbenefit without requiring the prospective customer to manually enter anadditional coupon code beyond their key. Additionally, in the case ofcustom-generated hyperlinks tied to the customer's identity as describedin the discussion of the prepurchase event module, the coupon module hasthe ability to make a network call to the coupon module to check for thepresence of an applicable custom coupon code, and then with the priorconsent of the product controller, generate custom hyperlinks that areautomatically aware of the coupon code so that this information may beautomatically recognized by the purchase module.

The Subscriber Module

The subscriber module is able to provide a subscriber function thatcustomers are able to select and enter contact information (and/orselect an existing account with associated contact information) and theproduct release system is operative to deliver messages and/or benefitsto the customers that have subscribed (as stored in a subscriberdatabase). In particular, each of the subscribers lists are able to beassociated with a product controller (e.g. product controller account)and/or a product, type of product or related products (e.g. a particularebook, ebooks generally or an ebooks series) and provided benefitsassociated with that creator and/or product, type of product or relatedproducts.

Additionally, as described above, the product release platform 99 isable to present existing subscription lists associated with a productcontroller account (and/or products thereof) for selection by theproduct controller (when creating an event) as target customers for thatevent. The product release platform 99 is then able to transmit keys foror otherwise make the event (e.g. prepurchase or prepurchase presale)available to those target customers (in one or more of the mannersdescribed above).

The Event Bid Module

The event bid module enables a product controller account to identifyone or more events of the account as “bid events” and one or more otheraccounts (e.g. accounts of one or more online merchants) to bid for, ornegotiate for, the right to list and host the prepurchase andprepurchase preorder events, either exclusively or non-exclusivity.Additionally, the event bid module is able to enable accounts (e.g.accounts of third party servers 112, online merchants and/or thedistributors that supply online merchants) to upload a standardized menuof preferential terms that the module enables the product controlleraccounts to optionally accept for one or more products of that account.These terms are then able to be automatically applied based oncharacteristics of a prepurchase event. The characteristics are able tocomprise one or more of: the type of product; track record or reputationof the product controller; length of the prepurchase event; the numberof days for which the prepurchase event represents early access comparedto the general release date; performance of the general releasepreorder, and or the level of exclusivity (none, partial, full); and theincentives offered to the product controller may comprise one or more ofpreferential merchandising, marketing and/or discoverability within theproduct release server 102 and/or a third party server's 112 catalog;targeted email marketing to the product release server 102 and/or athird party server's 112 customers; payment of an advance by the productrelease server 102 and/or a third party server 112 (e.g. merchant ordistributor) to the product controller for the right to carry (list) andexecute the prepurchase event; improved payment terms compared to anordinary single public release event (e.g. to the creator or theirrepresentative, higher royalties or margins, lower commissions or fees,more favorable payment terms); the promise or consideration of featuredpromotion at the product release server 102 and/or a third party server112 and/or inclusion in special merchandising features; or otheradvantages in exchange for the product controller agreeing to make theirprepurchase event available to the product release server 102 and/or athird party server's 112 customers or subscribers. As a result, themodule provides the advantage of enabling the product controller toenroll their product at favorable predetermined terms on a self-servebasis without requiring any person-to-person negotiation, therebyenabling the product release server 102 and/or a third party server 112to source these valuable prepurchase event listings at scale.

The Inventory Module

The inventory module is able to monitor the customer-fulfillableinventory status. The inventory module is able to have applicationprogramming interface (API) hooks that allow it to access and displayinventory data stored in inventory management systems. The inventorymodule is able to display inventory levels of customer-fulfillableproduct at any time during the product controller's creation of theirprepurchase or prepurchase preorder event, and at any time leading up toor during the prepurchase or prepurchase preorder events, and ifnecessary prompt or remind the product controller to deliver product bythe agreed-upon deadlines, per the custom terms specified to the productcontroller when the product controller was setting up their event. Asthe event activation or release dates approach, other modules of theproduct release platform 99, working in concert with the inventorymodule, are able to transmit messages to the inventory module tounderstand if the product controller has delivered the product;otherwise the prepurchase event is able to be automatically delayed orcancelled.

Method of Operation

FIG. 5 illustrates a method of enabling prepurchase of one or moreproducts via one or more product release servers 102 according to someembodiments. As shown in FIG. 5, the product release platform 99generates a product listing identifying a product based on product datareceived from a third party product controller device 104 at the step502. In some embodiments, the product data includes a content filecontaining the product, a product release date, and metadata associatedwith the product and the content file. The product release platform 99generates one or more prepurchase keys and one or more prepurchaseevents based on prepurchase data for the product input by the thirdparty product controller device 104 at the step 504. Alternatively, thestep 504 is able to be omitted for non-private events. In someembodiments, the prepurchase data includes a starting time, one or moreend conditions and pricing data for each of the prepurchase events. Insome embodiments, the prepurchase data includes a selection of one ormore entries of customer contact data and the product release platform99 automatically transmits the keys to the locations identified by thecustomer contact data. For each of the prepurchase events, the productrelease platform 99 facilitates the sales of the product to one or morecustomer devices 106 during the prepurchase event if one or more keyssubmitted by the customer devices 106 correspond to the prepurchase keysassociated with the prepurchase event and preventing sales if they donot at the step 506. The product release platform 99 then delivers theproduct to the one or more customer devices 106 after the transaction iscomplete at the step 508.

In some embodiments, the method further comprises the product releaseplatform 99 generating one or more prepurchase preorder keys and one ormore prepurchase preorder events based on prepurchase preorder data(stored in a preorder database) for the product indicated by thecustomer device 106. In some embodiments, the prepurchase preorder dataincludes information that identifies one of the prepurchase events. Insome embodiments, the method further comprises the product releaseplatform 99, for each of the prepurchase preorder events, facilitatingordering of the product by one or more customer devices 106 during theprepurchase preorder event if one or more prepurchase preorder keyssubmitted by the customers correspond to the prepurchase preorder keysassociated with the prepurchase preorder event and preventing orderingof the product by the customer devices 106 if not. In some embodiments,the method further comprises the product release platform 99automatically facilitating the purchase of the product by the one ormore customer devices 106 that ordered the product during the identifiedone of the prepurchase events.

In some embodiments, the method further comprises the product releaseplatform 99 terminating the prepurchase event upon reaching the timeindicated by the end condition. In some embodiments, the method furthercomprises the product release platform 99 dynamically adjusting theprice indicated on the prepurchase event page based on a pricing metricof the pricing data. In some embodiments, the method further comprisesthe product release platform 99 preventing sales of the product to theconsumer devices 106 even if the submitted key corresponds to theprepurchase keys associated with the prepurchase event if the one ormore of the consumers have not satisfied the prepurchase conditionsdefined in the prepurchase data. In some embodiments, the method furthercomprises the product release platform 99 enabling the selection of allor a subset of customer contact information of the product controller'saccount and automatically transmitting the prepurchase key to networkaccessible locations identified by the subset of the one of the sets ofcustomer contact information.

In some embodiments, the method further comprises the product releaseplatform 99 collecting the contact information submitted to satisfy theprepurchase conditions and adding it to the sets of customer contactinformation of the account associated with the prepurchase event (e.g.the account of the product controller who created the prepurchaseevent). In some embodiments, the method further comprises the productrelease platform 99 generating a prepurchase page (e.g. webpage,application page) that identifies the product based on the metadata, therelease date of the product and the starting time of the prepurchaseevent. As a result, the method provides the advantage of enablingproduct controllers to directly generate, modify and control customizedprepurchase events for the sales of their products. Additionally,although the method of FIG. 5 includes steps 502-508, one or more of thesteps are able to be omitted, rearranged and/or additional steps areable to be added including one or more of the features described herein.

FIG. 6 illustrates a method of a customer device 106 purchasing aproduct via a prepurchase event according to some embodiments. As shownin FIG. 6, the customer device 106 creates an account on the productrelease server 102 at the step 602. Alternatively, the customer device106 is able to use a guest account in which the complete or partialaccount registration process is integrated into the shopping cartpurchase process, or step 602 is able to be omitted if an account hasbeen previously created. The customer device 106 accesses theprepurchase product on the product release server 102 at the step 604.In some embodiments, the price of the product on the prepurchase eventpage is dynamically adjusted by the server based on the pricing data ofthe prepurchase event. In some embodiments, the customer 106 accessesthe prepurchase product by accessing a prepurchase event page, a productlisting from a dedicated page or from a catalog of one or more products,and/or a hyperlink that links to the prepurchase event page. The productdata and/or the prepurchase event data are able to be stored in one ormore databases on the product release server 102. For privateprepurchase events, the customer device 106 submits the key and theproduct release server 102 verifies that the key corresponds to one ormore of the keys for that prepurchase event at the step 606.

Specifically, the product release server 102 is able to verify the keyby determining that the key matches or corresponds to one of the keysfor the prepurchase event stored in a prepurchase database, or, in thecase of single-use keys tied to an individual customer, the productrelease server 102 verifies that the customer's identity (e.g. asdetermined by email address or login credentials) matches the identityof the customer as known by the product release server. Alternatively,the customer device 106 is able to submit the key when attempting toaccess the prepurchase page in step 604 and is granted or withheldaccess to the page based on whether the key is verified by the productrelease server 102. Alternatively, step 606 is able to be omitted if theevent is not a private event. In some embodiments, the product releaseserver 102 further determines if the customer device 106 has satisfiedsome or all of the conditions associated with the prepurchase event andadjusts the product price and/or permits/prevents the purchase of theproduct based on which of the conditions are satisfied.

If the key is validated by the product release server 102, the productis added to the shopping cart database for the customer at the step 608.The customer device 106 then authorizes or executes the submission ofpayment information to the payment processor 110 for the product eitherdirectly or via the product release server 102 at the step 610. Thepayment processor validates the payment order and transmits the paymentor payment credit indicated by the payment information to the servers102 at the step 612 (if the payment method or amount is fails validationof the payment processor, the payment process reports back to theproduct release server 102 since payment is one of the conditions forauthorizing the completion of a product purchase, and the purchase isdenied until the customer corrects the problem.

Once an order is approved by the payment processor, the product releaseserver 102 completes the order using an order database and removes theproduct from the shopping cart database of the customer at the steps 614and 616. Finally, the product release server 102 makes available and/orinitiates delivery of the product to the customer at the step 618. Insome embodiments, the product file is transmitted to the customer'sdevice 106. Alternatively, the product file is able to be transferred toa customer account database associated with the product release server102 and/or stored for access via a cloud storage repository, such thatthe file becomes available for download and/or streaming to thecustomer's device 106. As a result, the method provides the advantage ofenabling sellers to generate and manage custom prepurchase events wherecustomers are able to purchase and take receipt of new products beforethe products are available to the general public.

Advantages

Thus, the product release system 100 described herein has numerousadvantages. Specifically, the system provides the advantage ofimprovement in the technical field of ecommerce by providing theunconventional feature of enabling a user to generate product listingswith generalized release dates along with customized prepurchase events.

Conventional internet-based product releasing entities provide featuresthat are largely controlled by the entities themselves (e.g. featuresthat are created by the entities themselves and often hard coded suchthat product controllers are limited to the predefined functionspresented by on the institution website). In contrast, in the describedproduct release system 100 product controllers themselves are enabled todesign and adjust the features and in particular to generate andcustomize one or more prepurchase events in order to list, launch andsell their product. As a result, the product release functions are ableto be as dynamic as needed for each product controller, rather thangenerically forced by the institution and limited to its functionaldecisions. Thus, the technical field is improved as new product releasesare no longer constrained by the limitations of a single product releasedate.

In other words, the system, method and device provide the benefit ofenabling controllers of physical or digital goods and services tocreate, update and manage product listings that are a part of theproduct release server 102 and/or a third party server's 112 catalog,whereby such product listings are able to support a plurality of productrelease events including prepurchase events. The system, method anddevice provide the benefit of an interface by which prospectivecustomers can browse, consider, purchase and receive said products orservices utilizing the generated prepurchase events.

Additionally, the product release system enables a more expansivetemporal timeline for new product introductions conducted over ecommercethan is possible with the conventional approach to new productintroductions.

Early access has value and appeal to consumers, and this system enablesproduct controllers to exploit that value while also adding value andexcitement to the customer's purchase experience. This system willenable the entire ecommerce supply chain to benefit from this importantnew method of product launch marketing, and importantly and necessarily,to do it at scale. Scale matters, because without the ability for theproduct release server 102 and/or a third party server 112 toefficiently publish and update product listings for upcoming newproducts that may offer a theoretically unlimited number of prepurchaseevents and support a theoretically unlimited number of product listingupdates by the product controller (i.e. updates/changes to a productlisting as controlled by the product controller), and without theability to quickly update and publish these dynamic listings the productcontroller can change at any time, these millions of product controllersand their billions of consumers would be shut out of this excitingopportunity to benefit from prepurchase events.

The system is able touch key members of the product supply chaininvolved in helping product controllers take their new products tomarket via ecommerce. This disclosure describes a product release systemthat can be operated by an online merchant, a product creator, adistributor and/or other entity and/or by multiple members of theproduct supply chain in isolation or in cooperation. The systems,methods and devices disclosed herein enable product controllers tofracture the conventional timeline of new product introductions, whereproduct launches are treated as one-time events, by transforming thesingle product launch into multiple launch events that can be targetedat different customer segments, and each launch event able to activateon different dates with different incentives and purchase conditionscalibrated to the product marketing goals of the product controller.These individually marketable product launch events are executed at theproduct release server 102 and/or a third party server 112 under theshared control of the product controllers. The present invention offersthe creators of new products and services myriad new customizableopportunities to make their products visible, differentiatable anddesirable to more customers. Product controllers can leverage thecustomer allure of early access to new products to forge greatercustomer satisfaction and loyalty.

The present invention has been described in terms of specificembodiments incorporating details to facilitate the understanding ofprinciples of construction and operation of the invention. Suchreference herein to specific embodiments and details thereof is notintended to limit the scope of the claims appended hereto. It will bereadily apparent to one skilled in the art that other variousmodifications may be made in the embodiments chosen for illustrationwithout departing from the spirit and scope of the invention as definedby the claims. For example, although the platform is described as havinga separate product database (storing product data), prepurchase eventdatabase (storing prepurchase data), user database (storing user accountinformation and/or user contact information), orders database (storingpreorder information), shopping cart database and/or other databases, itis understood that one or more of the databases are able to be combinedand/or split into separate databases. Additionally, it is understoodthat although the platform is described as comprising various modules,the names of these modules are arbitrary. The module labels are anartificial construct to assist those skilled in the art to gain a fulland transparent understanding of the systems, methods and devices thatcomprise the invention. It is understood that those skilled in the arthave the ability to mix and match the functions embodied within themodules, or to abandon the module concept altogether. Further, althoughthe description above relates primarily to the sales and/or purchase ofthe products and/or services, these sales and/or purchases are able tobe replaced and/or supplemented with rentals, leases, subscriptionsand/or other types of transactions related to the products/services(e.g. where ownership of the products/services is not fully conveyed asit is in a sale, or product access is ephemeral).

In some embodiments, the product release system described herein is ableto be operated independently by multiple supply chain participants,while also allowing the operators of these independent systems tocollaborate on the creation and execution of the same prepurchase event.For example, a product creator may use a distributor-operated portion ofthe product release system to supply their distributor the product,product data and event data associated with an upcoming product launchevent. The distributor will then distribute the product, product dataand event data to one or more online merchants, who will then use thisdata and the product assets to construct the product listings by whichthe merchant will merchandise one or more launch events (a generalrelease event and one or more prepurchase events) to its customers. Inthis example, the product creator's relationship is with thedistributor, not the merchant, and the distributor assumes certain tasksand responsibilities so that the merchant doesn't have to. Thus,different supply chain participants are able to collaborate by utilizingdifferent aspects of the same product release system.

In some embodiments, if the product creator were not working with adistributor, and instead working directly with a merchant-operatedproduct release system, then the merchant's portion of the productrelease system is able to handle the full range of product releasesystem capabilities, from ingestion and validation of product listingsto the merchandising and fulfillment of the products to customers. Thesupply chain participants employing various aspects of the productrelease system described herein as product controllers are able tocomprise product creators (e.g. manufacturers, brands, publishers,independent authors, musicians, artists, rights holders, craftspeople,service providers, sellers or other types of product creators),distributors (i.e. companies that aggregate products and product data onbehalf of multiple product creators, and supply these products andproduct listings to one or more online merchants) and online merchants(i.e. companies that sell or provide products and/or services directlyto end customers, such as online retailers, online marketplaces,subscription services, streaming services, app stores, and/or anywebsite or mobile app with ecommerce capabilities), to generate andadminister customized prepurchase events at scale giving customers—orcertain selected subgroups of customers—the opportunity to browse,purchase and/or access or receive upcoming new products before theirofficial product introduction dates.

As described above, the products described herein are able to comprisedigital books (e.g. ebooks). Alternatively or in addition, the productsare able to comprise physical/non-digital products or services that canbe sold over ecommerce networks to end consumers. For example, theproducts are able to comprise any new physical or digital product orservice that has a scheduled future general release date and can bemerchandised online, such as, but not limited to, printed books;apparel; toys; electronics; food and beverages; consulting services;financial products and services; travel & hospitality services includinglodging; real estate, ebooks; recorded audio such as audio books,podcasts, and music; video and filmed entertainment; educationalcourseware; downloadable applications and software; packaged software;video games; artwork and images; and other products and combinationsthereof. Also, for the avoidance of any confusion, the events describedthroughout this disclosure are able to comprise product release datesand preorder periods. For example, when a future product introductiongoes on preorder, or on prepurchase, it is able to be referred to as apreorder event, or a prepurchase event, and that event is able tocomprise a start date and an end date, and for the duration of theseevents prospective customers, if authorized, are able to place purchaseorders that entitle them to receive the forthcoming new productintroductions earlier than the general public. As described herein, theterm “page” is able to refer to a webpage, a website, an applicationscreen/page, a user interface and/or any other type of digital page.

Additionally, although some examples in the description herein focus ondigital book products (e.g. ebooks), it is understood that the productsare able to be other digital products. Alternatively, in someembodiments the products are able to be physical products in addition toor instead of digital products. In such embodiments, it is understoodthat the delivery of the physical product involves the facilitation of aphysical delivery (packaging, routing, medium, and other deliveryparameters), rather than a digital delivery as described herein.

What is claimed is:
 1. A product release system for enabling prepurchaseof one or more products, the product release system comprising: one ormore servers including a processor and a non-transitorycomputer-readable medium coupled with the processor, storing a productrelease platform having a platform user interface and able to becommunicatively coupled with one or more third party devices over anetwork, wherein the product release platform is operable to: generate aproduct listing identifying a new product based on product data receivedfrom a third party device, wherein the product data includes a productrelease date that is in the future, and metadata associated with the newproduct; provide the platform user interface for generating aprepurchase event, wherein the platform user interface: displays a setof product listings including the product listing identifying the newproduct, the set of product listings associated with a productcontroller account on the product release platform; enables selection,with the product controller account, of the product listing identifyingthe new product from the set of product listings for the prepurchaseevent; enables input of pricing data for the prepurchase event with theproduct controller account; enables selection of a starting time for theprepurchase event with the product controller account; and enablesselection of an end condition for the prepurchase event with the productcontroller account; receive selections of the new product, the startingtime and the end condition and input of the pricing data; generate theprepurchase event based on the new product, the starting time, the endcondition and the pricing data, wherein the prepurchase event includes apurchase function that enables one or more customers to complete apurchase transaction to purchase and obtain the new product before theproduct release date, wherein the starting time is before the productrelease date; generate one or more prepurchase keys for the one or moreprepurchase events, wherein completion of the purchase transactionprovided by the prepurchase events requires input of one or more of theprepurchase keys; and for the prepurchase event: receive one or moreinput keys from the one or more customers; determine if the one or moreinput keys correspond to the prepurchase keys associated with theprepurchase event; in advance of the product release date, facilitatepurchase of the new product by the one or more customers using thepurchase function to complete the purchase transaction and provideaccess to the new product to the one or more customers upon completionof the purchase transaction during the prepurchase event if the one ormore input keys correspond to the prepurchase keys associated with theprepurchase event; and prevent purchase of the new product by the one ormore customers during the prepurchase event if the one or more inputkeys do not correspond to the prepurchase keys associated with theprepurchase event, wherein the product release platform preventspurchase of the new product by rejecting the purchase transaction forthe new product initiated by the one or more customers with the purchasefunction of the prepurchase event.
 2. The product release system ofclaim 1, wherein each input key of the one or more input keys isincluded within a hyperlink that links to a page associated with theprepurchase event of the input key and submits the input key to theproduct release platform for determining if the input key corresponds tothe prepurchase keys associated with the prepurchase event.
 3. Theproduct release system of claim 1, wherein the end condition is one ormore of an end time, a quantity of sales, a maximum quantity ofcustomers accessing the prepurchase event, an inventory status of thenew product, and a manual cancellation of the event, and furtherwherein, upon reaching the end condition the product release platform isoperable to terminate the prepurchase event.
 4. The product releasesystem of claim 1, wherein the pricing data is a pricing metric thatindicates a price value for the starting time and at least one differentprice value for one or more subsequent times between the starting timeand an end of the prepurchase event as indicated by the end condition.5. The product release system of claim 1, wherein each of theprepurchase events include one or more prepurchase conditions, andfurther wherein the product release platform is operable to preventsales of the new product to one or more of the customers even if theinput key corresponds to the prepurchase keys associated with theprepurchase event if the one or more of the customers have not satisfiedthe prepurchase conditions.
 6. The product release system of claim 5,wherein the prepurchase conditions comprise one or more of submittingcontact information, purchasing or subscribing to one or more otherproducts, spending a threshold amount of money, and agreeing to a termsof use of the new product.
 7. The product release system of claim 6,wherein the product release platform is operable to add the contactinformation submitted to satisfy the prepurchase conditions of theprepurchase event to the product controller account.
 8. The productrelease system of claim 1, wherein the product release platform isoperable to generate a prepurchase listing that identifies the newproduct based on the metadata and the product release date of the newproduct.
 9. The product release system of claim 1, wherein the productrelease platform is operable to: generate one or more prepurchasepreorder keys; generate one or more prepurchase preorder events that areeach based on one of one or more prepurchase events and include aprepurchase event identifier of the one of the prepurchase events, astart date and an end date that are both prior to the start time of theone of the prepurchase events and a preorder function that enables theone or more customers to preorder a purchase of the new product duringthe one of the prepurchase events; for each of the prepurchase preorderevents, facilitate preordering of the new product by one or morecustomers during the prepurchase preorder event using the preorderfunction if one or more prepurchase preorder keys submitted by thecustomers correspond to the prepurchase preorder keys associated withthe prepurchase preorder event and prevent preordering of the newproduct by the one or more customers during the prepurchase preorderevent if the one or more prepurchase preorder keys submitted by thecustomers do not correspond to the prepurchase preorder keys associatedwith the prepurchase preorder event; and in response to preordering ofthe new product by the one or more customers using the preorderfunction, facilitate the preordered purchase of the new product by theone or more customers during the identified one of the prepurchaseevents using the purchase function of the one of the prepurchase events.10. The product release system of claim 1, wherein the product dataincludes a content file containing the new product and the content filecomprises one or more of the group consisting of: a product, an image, avideo, audio, a computer application.
 11. A method of enablingprepurchase of one or more products via one or more product releaseservers, the method comprising: generating, with the product releaseservers, a product listing identifying a new product based on productdata received from a third party device, wherein the product dataincludes a product release date that is in the future, and metadataassociated with the new product; providing, with the product releaseservers, a platform user interface for generating a prepurchase event,wherein the platform user interface: displays a set of product listingsincluding the product listing identifying the new product, the set ofproduct listings associated with a product controller account on theproduct release platform; enables selection, with the product controlleraccount, of the product listing identifying the new product from the setof product listings for the prepurchase event; enables input of pricingdata for the prepurchase event with the product controller account;enables selection of a starting time for the prepurchase event with theproduct controller account; and enables selection of an end conditionfor the prepurchase event with the product controller account; receivingselections of the new product, the starting time, the end condition andthe pricing data; generating the prepurchase event based on the newproduct, the starting time, the end condition and the pricing data,wherein the prepurchase event includes a purchase function that enablesone or more customers to complete a purchase transaction to purchase andobtain the new product before the product release date, wherein thestarting time is before the product release date; generating, with theproduct release servers, one or more prepurchase keys for theprepurchase event, wherein completion of the purchase transactionprovided by the prepurchase events requires input of one or more of theprepurchase keys; receiving, with the product release servers, one ormore keys from the one or more customers; determining, with the productrelease servers, if the one or more input keys correspond to theprepurchase keys associated with the prepurchase event; in advance ofthe product release date with the product release servers, facilitatingpurchase of the new product by the one or more customers using thepurchase function to complete the purchase transaction and provideaccess to the new product to the one or more customers upon completionof the purchase transaction during the prepurchase event if the one ormore input keys correspond to the prepurchase keys associated with theprepurchase event; and preventing, with the product release servers,purchase of the new product to the one or more customers during theprepurchase event if the one or more input keys do not correspond to theprepurchase keys associated with the prepurchase event, wherein thepreventing of purchase of the new product includes rejecting thepurchase transaction for the new product initiated by the one or morecustomers with the purchase function of the prepurchase event.
 12. Themethod of claim 11, wherein each input key of the one or more input keysis included within a hyperlink that links to a page associated with theprepurchase event of the input key and submits the input key to theproduct release servers for determining if the input key corresponds tothe prepurchase keys associated with the prepurchase event.
 13. Themethod of claim 11, wherein the end condition is one or more of an endtime, a quantity of sales, a maximum quantity of customers accessing theprepurchase event, an inventory status of the new product and manualcancellation of the event, and further wherein upon reaching the endcondition the product release platform is operable to terminate theprepurchase event.
 14. The method of claim 11, wherein the pricing datais a pricing metric that indicates a price value for the starting timeand at least one different price value for one or more subsequent timesbetween the starting time and an end of the prepurchase event asindicated by the end condition.
 15. The method of claim 11, wherein theprepurchase event includes one or more prepurchase conditions, furthercomprising preventing sales of the new product to one or more of thecustomers with the product release servers even if the input keycorresponds to the prepurchase keys associated with the prepurchaseevent if the one or more of the customers have not satisfied theprepurchase conditions.
 16. The method of claim 15, wherein theprepurchase conditions comprise one or more of submitting contactinformation, purchasing or subscribing to one or more other products,spending a threshold amount of money and agreeing to a terms of use ofthe new product.
 17. The method of claim 16, further comprising addingthe contact information submitted to satisfy the prepurchase conditionsof the prepurchase event to the product controller account.
 18. Themethod of claim 11, further comprising generating with the productrelease servers a prepurchase listing that identifies the new productbased on the metadata, the release date of the new product and thestarting time of the prepurchase event.
 19. The method of claim 11,further comprising, with the product release servers: generating one ormore prepurchase preorder keys; generating one or more prepurchasepreorder events that are each based on one of one or more prepurchaseevents and include a prepurchase event identifier of the one of theprepurchase events, a start date and an end date that are both prior tothe start time of the one of the prepurchase events and a preorderfunction that enables the one or more customers to preorder a purchaseof the new product during the one of the prepurchase events; for each ofthe prepurchase preorder events, with the product release servers,facilitating preordering of the new product by one or more customersduring the prepurchase preorder event using the preorder function if oneor more prepurchase preorder keys submitted by the customers correspondto the prepurchase preorder keys associated with the prepurchasepreorder event and preventing preordering of the new product by the oneor more customers during the prepurchase preorder event if the one ormore prepurchase preorder keys submitted by the customers do notcorrespond to the prepurchase preorder keys associated with theprepurchase preorder event; and in response to preordering of the newproduct by the one or more customers using the preorder function,facilitate the preordered purchase of the new product by the one or morecustomers during the identified one of the prepurchase events with theproduct release servers using the purchase function of the one of theprepurchase events.
 20. The method of claim 11, wherein the product dataincludes a content file containing the new product and the content filecomprises one or more of the group consisting of: a product, an image, avideo, audio, a computer application.
 21. A non-transitorycomputer-readable medium storing a product release platform configuredto: generate a new product listing identifying a new product based onproduct data received from a third party device, wherein the productdata includes a product release date that is in the future, and metadataassociated with the new product; provide a platform user interface forgenerating a prepurchase event, wherein the platform user interface:displays a set of product listings including the product listingidentifying the new product, the set of product listings associated witha product controller account on the product release platform; enablesselection, with the product controller account, of the product listingidentifying the new product from the set of product listings for theprepurchase event; enables input of pricing data for the prepurchaseevent with the product controller account; enables selection of astarting time for the prepurchase event with the product controlleraccount; and enables selection of an end condition for the prepurchaseevent with the product controller account; receive selections of the newproduct, the starting time and the end condition and input of thepricing data; generate the prepurchase event based on the new product,the starting time, the end condition and the pricing data, wherein theprepurchase event includes a purchase function that enables one or morecustomers to complete a purchase transaction to purchase and obtain thenew product before the product release date, wherein the starting timeis before the product release date; generate one or more prepurchasekeys for the prepurchase event, wherein completion of the purchasetransaction provided by the prepurchase event requires input of one ormore of the prepurchase keys; receive one or more input keys from theone or more customers; determine if the one or more input keyscorrespond to the prepurchase keys associated with the prepurchaseevent; in advance of the product release date, facilitate purchase ofthe new product by the one or more customers using the purchase functionto complete the purchase transaction and provide access to the newproduct to the one or more customers upon completion of the purchasetransaction during the prepurchase event if the one or more input keyscorrespond to the prepurchase keys associated with the prepurchaseevent; and prevent purchase of the new product by the one or morecustomers during the prepurchase event if the one or more input keys donot correspond to the prepurchase keys associated with the prepurchaseevent, wherein the preventing of purchase of the new product includesrejecting the purchase transaction for the new product initiated by theone or more customers with the purchase function of the prepurchaseevent.
 22. The medium of claim 21, wherein each input key of the one ormore input keys is included within a hyperlink that links to a pageassociated with the prepurchase event of the input key and submits theinput key to the product release platform for determining if the inputkey corresponds to the prepurchase keys associated with the prepurchaseevent.
 23. The medium of claim 21, wherein the end condition is one ormore of an end time, a quantity of sales, a maximum quantity ofcustomers accessing the prepurchase event, an inventory status of thenew product and manual cancellation of the event, and further whereinupon reaching the end condition the product release platform is operableto terminate the prepurchase event.
 24. The medium of claim 21, whereinthe pricing data is a pricing metric that indicates a price value forthe starting time and at least one different price value for one or moresubsequent times between the starting time and an end of the prepurchaseevent as indicated by the end condition.
 25. The medium of claim 21,wherein the prepurchase event includes one or more prepurchaseconditions, and further wherein the product release platform is operableto prevent sales of the new product to one or more of the customers evenif the input key corresponds to the prepurchase keys associated with theprepurchase event if the one or more of the customers have not satisfiedthe prepurchase conditions.
 26. The medium of claim 25, wherein theprepurchase conditions comprise one or more of submitting contactinformation, purchasing or subscribing to one or more other products,spending a threshold amount of money and agreeing to a terms of use ofthe new product.
 27. The medium of claim 26, wherein the product releaseplatform is operable to add the contact information submitted to satisfythe prepurchase conditions of the prepurchase event to the productcontroller account.
 28. The medium of claim 21, wherein the productrelease platform is operable to generate a prepurchase page thatidentifies the new product based on the metadata, the release date ofthe new product and the starting time of the prepurchase event.
 29. Themedium of claim 21, wherein the product release platform is operable to:generate one or more prepurchase preorder keys; generate one or moreprepurchase preorder events that are each based on one of one or moreprepurchase events and include a prepurchase event identifier of the oneof the prepurchase events, a start date and an end date that are bothprior to the start time of the one of the prepurchase events and apreorder function that enables the one or more customers to preorder apurchase of the new product during the one of the prepurchase events;for each of the prepurchase preorder events, facilitate preordering ofthe new product by one or more customers during the prepurchase preorderevent using the preorder function if one or more prepurchase preorderkeys submitted by the customers correspond to the prepurchase preorderkeys associated with the prepurchase preorder event and preventpreordering of the new product by the one or more customers during theprepurchase preorder event if the one or more prepurchase preorder keyssubmitted by the customers do not correspond to the prepurchase preorderkeys associated with the prepurchase preorder event; and in response topreordering of the new product by the one or more customers using thepreorder function, facilitate the preordered purchase of the new productby the one or more customers during the identified one of theprepurchase events using the purchase function of the one of theprepurchase events.
 30. The medium of claim 21, wherein the product dataincludes a content file containing the product and the content filecomprises one or more of the group consisting of: a product, an image, avideo, audio, a computer application.
 31. A product release system forenabling prepurchase of one or more products, the product release systemcomprising: one or more servers including a processor and anon-transitory computer-readable medium coupled with the processor,storing a product release platform having a platform user interface andable to be communicatively coupled with one or more third party devicesover a network, wherein the product release platform is operable to:generate a product listing identifying a new product based on productdata received from a third party device, wherein the product dataincludes a product release date that is in the future, and metadataassociated with the new product; provide the platform user interface forgenerating a prepurchase event, wherein the platform user interface:displays a set of product listings including the product listingidentifying the new product, the set of product listings associated witha product controller account on the product release platform; enablesselection, with the product controller account, of the product listingidentifying the new product from the set of product listings for theprepurchase event; enables input of pricing data for the prepurchaseevent with the product controller account; enables selection of astarting time for the prepurchase event with the product controlleraccount; enables selection of an end condition for the prepurchase eventwith the product controller account; and enables the adjustment of thestarting time, the end condition and the pricing data of the prepurchaseevent; receive selections of the new product, the starting time and theend condition and input of the pricing data; generate the prepurchaseevent based on the new product, the starting time, the end condition andthe pricing data, wherein the prepurchase event includes a purchasefunction that enables one or more customers to complete a purchasetransaction to purchase and obtain the new product before the productrelease date, wherein the starting time is before the product releasedate; and in advance of the product release date, facilitate purchase ofthe new product by the one or more customers using the purchase functionto complete the purchase transaction and provide access to the newproduct to the one or more customers upon completion of the purchasetransaction during the prepurchase event.
 32. The product release systemof claim 31, wherein the end condition is one or more of an end time, aquantity of sales, a maximum quantity of customers accessing theprepurchase event, an inventory status of the new product and a manualcancellation of the event, and further wherein upon reaching the endcondition the product release platform is operable to terminate theprepurchase event.
 33. The product release system of claim 31, whereinthe pricing data is a pricing metric that indicates a price value forthe starting time and at least one different price value for one or moresubsequent times between the starting time and an end of the prepurchaseevent as indicated by the end condition.
 34. The product release systemof claim 31, wherein the prepurchase event includes one or moreprepurchase conditions, and further wherein the product release platformis operable to prevent sales of the new product to one or more of thecustomers if the one or more of the customers have not satisfied theprepurchase conditions, wherein the product release platform preventspurchase of the new product by rejecting the purchase transactions forthe new product initiated by the one or more customers with the purchasefunction of the prepurchase event.
 35. The product release system ofclaim 34, wherein the prepurchase conditions comprise one or more ofsubmitting contact information, purchasing or subscribing to one or moreother products, spending a threshold amount of money and agreeing to aterms of use of the new product.
 36. The product release system of claim31, wherein the product release platform is operable to generate aprepurchase page that identifies the new product based on the metadata,the release date of the new product and the starting time of theprepurchase event.
 37. The product release system of claim 31, whereinthe product release platform is operable to: generate one or moreprepurchase preorder events based on one of one or more prepurchaseevents and prepurchase preorder data for the new product indicated bythe third party device, wherein the prepurchase preorder events includea preorder function that enables the one or more customers to preorder apurchase of the product during the one of the prepurchase events, andfurther wherein the prepurchase preorder data includes information thatidentifies the one of the prepurchase events; for each of theprepurchase preorder events, facilitate preordering of the new productby one or more customers during the prepurchase preorder event using thepreorder function; and in response to preordering of the new product bythe one or more customers using the preorder function, facilitate thepreordered purchase of the new product by the one or more customersduring the identified one of the prepurchase events using the purchasefunction of the one of the prepurchase events.
 38. The product releasesystem of claim 31, wherein the product data includes a content filecontaining the product and the content file comprises one or more of thegroup consisting of: a product, an image, a video, audio, a computerapplication.